Your problem is quite simple if you read the output carefully. You have the cross-compiler installed in: > Reading specs from /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/specs
and another hint: > gcc version 3.0 > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/cc1 -lang-c -v -iprefix > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/ -D__GNUC__=3 -D__GNUC_MINOR__=0 > While the cross-compile toolchain expects to be in: /usr/local/arm/3.0 > GNU CPP version 3.0 (cpplib) (ARM GNU/Linux with ELF) > GNU C version 3.0 (arm-linux) > compiled by GNU C version 2.95.2 20000220 (Debian GNU/Linux). > ignoring nonexistent directory This should trigger you now "nonexsistent directory". The compiler is looking in "/usr/local/arm/3.0/lib/gcc-lib/arm-linux/3.0/include but cannot find the directory. > "/usr/local/arm/3.0/lib/gcc-lib/arm-linux/3.0/include" > ignoring nonexistent directory > "/usr/local/arm/3.0/lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/sys-include" > ignoring nonexistent directory > "/usr/local/arm/3.0/lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/include" > #include "..." search starts here: > #include <...> search starts here: > /usr/cross-3.0/lib/gcc-lib/arm-linux/3.0/include > /usr/cross-3.0/arm-linux/sys-include > /usr/cross-3.0/arm-linux/include > End of search list. The final most convincing error message is the last line of this block. It definite says "cannot find */usr/local/arm/3.0/arm-linux/lib/libc.so.g" > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/lib/crtn.o > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/bin/ld: > cannot find /usr/local/arm/3.0/arm-linux/lib/libc.so.6 The compiler is looking in /usr/local/arm/3.0 instead of /usr/cross-3.0/bin. My guess install the toolchain in /usr/local/arm/ and all should go well. Hope this solves your problem ;-) Greetings, Jean-Paul Saman. ======================================= [EMAIL PROTECTED] wrote: > > I already installed a prebuilt toolchain version 3.0. I created a simple "hello > world" program and compiled it using my cross compiler toolchain. > I got this message: > > [root@dhcp-72-88 /root]# vi hello.c > [root@dhcp-72-88 /root]# arm-linux-gcc -v -o helloarm hello.c > Reading specs from /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/specs Where cross-compiler is installed > Configured with: ../../src/gcc-3.0/configure --target=arm-linux > --prefix=/usr/local/arm/3.0 --enable-languages=c,c++,objc,f77,java > --enable-threads > Thread model: posix > gcc version 3.0 > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/cc1 -lang-c -v -iprefix > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/ -D__GNUC__=3 -D__GNUC_MINOR__=0 > -D__GNUC_PATCHLEVEL__=0 -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ > -D__ELF__ -D__unix -D__linux -Asystem=unix -Asystem=posix -Acpu=arm > -Amachine=arm -D__CHAR_UNSIGNED__ -D__NO_INLINE__ -D__STDC_HOSTED__=1 > -D__ARM_ARCH_3__ -D__APCS_32__ -D__ARMEL__ -D__arm__ hello.c -quiet -dumpbase > hello.c -version -o /tmp/ccWHxwFa.s > GNU CPP version 3.0 (cpplib) (ARM GNU/Linux with ELF) > GNU C version 3.0 (arm-linux) > compiled by GNU C version 2.95.2 20000220 (Debian GNU/Linux). > ignoring nonexistent directory Cannot find where it expect things to be. > "/usr/local/arm/3.0/lib/gcc-lib/arm-linux/3.0/include" > ignoring nonexistent directory > "/usr/local/arm/3.0/lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/sys-include" > ignoring nonexistent directory > "/usr/local/arm/3.0/lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/include" > #include "..." search starts here: > #include <...> search starts here: > /usr/cross-3.0/lib/gcc-lib/arm-linux/3.0/include > /usr/cross-3.0/arm-linux/sys-include > /usr/cross-3.0/arm-linux/include > End of search list. > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/bin/as -o > /tmp/cc8ANUOT.o /tmp/ccWHxwFa.s > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/collect2 -dynamic-linker > /lib/ld-linux.so.2 -X -m armelf_linux -p -o helloarm > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/lib/crt1.o > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/lib/crti.o > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/crtbegin.o > -L/usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0 > -L/usr/cross-3.0/bin/../lib/gcc-lib > -L/usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/lib > -L/usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../.. /tmp/cc8ANUOT.o -lgcc > -lc -lgcc /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/crtend.o > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/lib/crtn.o > /usr/cross-3.0/bin/../lib/gcc-lib/arm-linux/3.0/../../../../arm-linux/bin/ld: > cannot find /usr/local/arm/3.0/arm-linux/lib/libc.so.6 Looking where I expected things to be. But I cannot find it so giving up. > collect2: ld returned 1 exit status > [root@dhcp-72-88 /root]# > > Now, what seems to be my prblem now? I did not get the desired output. A file > seems to be missing from what is in the last part of the messages. Where can I > get that file. What links do I need to create? > > Thanks. > > Eman > > "Emmanuel_Arazo/Cebu/Lexmark.LEXMARK"@sweeper.lex.lexmark.com on 04/29/2002 > 08:25:11 PM > > To: [EMAIL PROTECTED] > cc: (bcc: Emmanuel Arazo/Cebu/Lexmark) > Subject: Re: Glibc compilation error > > Thank you for the encouragement. > Well for the record, this is the message I got: > > [root@localhost glibc-2.2.5]# CC=arm-linux-gcc ./configure arm-linux > --build=i686-pc-linux-gnu --prefix=/home/arm/glibc/arm-linux-glibc > --enable-add-ons --with-headers=/home/arm/linux-2.4.18/include > creating cache ./config.cache > checking host system type... arm-unknown-linux-gnu > checking sysdep dirs... sysdeps/arm/elf linuxthreads/sysdeps/unix/sysv/linux > linuxthreads/sysdeps/pthread sysdeps/pthread linuxthreads/sysdeps/unix/sysv > linuxthreads/sysdeps/unix linuxthreads/sysdeps/arm sysdeps/unix/sysv/linux/arm > sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman > sysdeps/unix/inet sysdeps/unix/sysv sysdeps/unix/arm sysdeps/unix > sysdeps/posix sysdeps/arm/fpu sysdeps/arm sysdeps/wordsize-32 > sysdeps/ieee754/flt-32 sysdeps/ieee754/dbl-64 sysdeps/ieee754 > sysdeps/generic/elf sysdeps/generic > checking for a BSD compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for pwd... /bin/pwd > checking build system type... i686-pc-linux-gnu > checking for arm-linux-gcc... arm-linux-gcc > checking version of arm-linux-gcc... v. ?.??, bad > checking for gnumake... no > checking for gmake... gmake > checking version of gmake... 3.79.1, ok > configure: error: > *** These critical programs are missing or too old:gcc > *** Check the INSTALL file for required versions. > [root@localhost glibc-2.2.5]# > > If I will try to continue what I am doing, what should I do? Why is it saying > that my gcc is old, eventhough I am already using the gcc version 3.0.4? > > Now for the prebuilt toolchains, I already have them. How will I be able to > install it, like what should I add in the configuration script for an arm target > or something like that. I had version 2.95.3 and 3.0 of the prebuilt toolchains. > Which is better to use? > > Thanks again. > > Eman > > Cam Mayor <[EMAIL PROTECTED]> on 04/29/2002 03:16:54 PM > > To: Ian Molton <[EMAIL PROTECTED]> > cc: [EMAIL PROTECTED] (bcc: > Emmanuel Arazo/Cebu/Lexmark) > Subject: Re: Glibc compilation error > > On Monday 29 April 2002 14:00, Ian Molton, risking a new somewhat off-topic > thread ;-) wrote: > > Russ Dill Awoke this dragon, who will now respond: > > > > Hope you can enlighten me concerning this. > > > > > > download a prebuilt toolchain > > > > You know... can we tone this down a bit? > > > > A /lot/ of people come here and ask for help compiling the toolchain. > > > > Geeks like to learn stuff. asking how to build it isnt an unreasonable > > question here, although best redirected to more appropriate forums... > > Ian, i hear what you're saying. as somebody who attempted to compile his own > cross compiler over weeks, slowly screwing up his system as he went, and > finally caved and went with the prebuilt toolchain...well, going with the > prebuilt toolchain was the smartest advice i took. i'm a nerd at heart and > love spending endless hours trying to figure out how stuff works, but at the > end of the day, i found i didn't care as much about compiling the compiler as > i did about getting my work done that necessitated the compiler. > > anyway, i can't speak for everybody, but when i have suggested people use the > prebuilt toolchain, it has been out of an honest desire to not see people > needlessly waste too much time. i think most "get the prebuilt" comments are > advising from that perspective. if they *really* want to get into the guts > of the toolchain, i'm sure they'll reply again, or go find the toochain > mailing list. > > cheers, > cam > > ------------------------------------------------------------------- > Subscription options: > http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel > FAQ/Ettiquette: http://www.arm.linux.org.uk/armlinux/mailinglists.php > > ------------------------------------------------------------------- > Subscription options: > http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel > FAQ/Ettiquette: http://www.arm.linux.org.uk/armlinux/mailinglists.php > > ------------------------------------------------------------------- > Subscription options: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel > FAQ/Ettiquette: http://www.arm.linux.org.uk/armlinux/mailinglists.php _______________________________________________ http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm http://www.arm.linux.org.uk/armlinux/mailinglists.php Please visit the above addresses for information on this list.
