IV config issue (ARM processor)

Post Reply
nima

IV config issue (ARM processor)

Post by nima »

Hi,
I am trying to compile neuron+interview on a system with ARM processor ( ARMv6-compatible processor rev 7 (v6l), with Debian-based OS). I get an error while I run the following. Any idea?
Thanks
Nima

$ /home/xxx/NEURON/iv-build/iv-18 > /home/xxx/NEURON/iv-source/iv-18/configure --prefix='/home/xxx/NEURON/iv-install/iv-18' |& tee c.txt

checking build system type... armv6l-unknown-linux-gnueabihf
checking host system type... armv6l-unknown-linux-gnueabihf
CYGWIN=no
MINGW=
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking how to print strings... printf
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert armv6l-unknown-linux-gnueabihf file names to armv6l-unknown-linux-gnueabihf format... func_convert_file_noop
checking how to convert armv6l-unknown-linux-gnueabihf file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking for gawk... no
checking for mawk... mawk
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for cos in -lm... yes
checking whether the compiler implements namespaces... yes
checking whether the compiler has stringstream... yes
The attempt to link a program with the statment
obuf.open(name, IOS_OUT);
failed. (Although it compiled in an earlier test).
Perhaps you need to add another library. eg setenv LIBS "-lstdc++".
Fix LIBS or src/include/ivstream.h.in in such a way that configure
does not stop here.
hines
Site Admin
Posts: 1682
Joined: Wed May 18, 2005 3:32 pm

Re: IV config issue (ARM processor)

Post by hines »

The attempt to link a program with the statment
obuf.open(name, IOS_OUT);
failed. (Although it compiled in an earlier test).
Perhaps you need to add another library. eg setenv LIBS "-lstdc++".
Fix LIBS or src/include/ivstream.h.in in such a way that configure
does not stop here.
You should look at config.log and see the precise reason the test failed. If it is not clear from that how to modify either LIBS or ivstream.h.in
then it will take some experimentation to figure out what to change. If you do not need graphics on this system, you can avoid InterViews
altoghether and go straing to configuring the nrn part using the configure option --without-x . That one, though, may stop at the same issue.
oren
Posts: 55
Joined: Fri Mar 22, 2013 1:03 am

Re: IV config issue (ARM processor)

Post by oren »

Look here.
http://www.neuron.yale.edu/phpbb/viewto ... f=6&t=2291

Maybe you can find some help there.
Post Reply