building NEURON on OSX 10.4 against X11
That is strange. On my machineAlthough I configured, built, and installed iv as you previously described, I can't run idemo because its linking assumes that libUnidrawhines.3.dylib and libIVhines.3.dylib are located in /usr/lib. nrniv, however, correctly assumes that said libraries are where I installed them (i.e., in /tmp/neuron/i686/lib).
otool -l idemo
gives
...
Load command 7
cmd LC_LOAD_DYLIB
cmdsize 80
name /Users/hines/neuron/ivx11/i386/lib/libIVhines.3.dylib (offset 24)
time stamp 1188860978 Mon Sep 3 19:09:38 2007
current version 4.3.0
compatibility version 4.0.0
which is consistent with the prefix I used
My machine is (from "about this mac") 10.4.10
2 GHz intel core duo
in iv/src config.guess yields
i386-apple-darwin8.10.1
which is, itself, a puzzle but is apparently what apple, autoconf
presently intend. And gcc --version gives
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5250)
2 GHz intel core duo
in iv/src config.guess yields
i386-apple-darwin8.10.1
which is, itself, a puzzle but is apparently what apple, autoconf
presently intend. And gcc --version gives
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5250)
I've uploaded a new
http://www.neuron.yale.edu/ftp/neuron/v ... -17.tar.gz
both iv and nrn should have a config.guess of i386 on the newer macs (why, I don't know).
http://www.neuron.yale.edu/ftp/neuron/v ... -17.tar.gz
both iv and nrn should have a config.guess of i386 on the newer macs (why, I don't know).
try downloading again. Every one of my versions of autoconf except the one on the mac generate a config.guess that returns i686 instead of i386. Either one is ok but it should be the same for both iv and nrn. i386 is useful since the configure for mpich2 on the mac also returns i386
in case you want to make use of the dual cores.
in case you want to make use of the dual cores.
Well then, I guess that was a wild goose chase. I re-uploaded an iv-17.tar.gz that
has a config.guess that returns i686.I was thinking that on your machine there were incompatible config.guess for iv and nrn. As long as they are both the same, that should not be a problem.
I must say that I am at a loss as to what is the cause of the missing nrniv windows under x11 on your machine. One way
to transcend the difficulty is to build iv and nrn with the --enable-carbon configure options. The only way I know to diagnose the x11 problem is to start adding printf statements in the code path between the hoc statement
objref g
g = new Graph()
and when the x11 window is mapped to the screen in the iv/src/lib/IV-X11/window.cpp file.
has a config.guess that returns i686.I was thinking that on your machine there were incompatible config.guess for iv and nrn. As long as they are both the same, that should not be a problem.
I must say that I am at a loss as to what is the cause of the missing nrniv windows under x11 on your machine. One way
to transcend the difficulty is to build iv and nrn with the --enable-carbon configure options. The only way I know to diagnose the x11 problem is to start adding printf statements in the code path between the hoc statement
objref g
g = new Graph()
and when the x11 window is mapped to the screen in the iv/src/lib/IV-X11/window.cpp file.