This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi Cristian, I'm replying your earlier letter, because it shows the problem most clearly. This is strange: >Making all in machine >make[6]: Entering directory >`/home/Cristian/b-gcc/arm-coff/newlib/arm-coff/be/ne >wlib/libc/machine' >Making all in i386 >make[7]: Entering directory >`/home/Cristian/b-gcc/arm-coff/newlib/arm-coff/be/ne >wlib/libc/machine/i386' >Assembler messages: >../../../../../../../../../gcc-2.95.2/newlib/newlib/libc/machin e/i386/memchr.S:1 >6: Error: bad instruction `pushl %ebp' What we see here is that the build has entered the newlib directory and is trying to build newlib for i386! Of course, the arm-coff assembler doesn't like all those x86 instructions. In fact, it's even stranger: the command that fails is ------snip----- /home/Cristian/b-gcc/gcc/xgcc -B/home/Cristian/b-gcc/gcc/ -B/bar/arm-coff/bin/ - idirafter /home/Cristian/b-gcc/arm-coff/newlib/targ-include -idirafter /home/Cri stian/gcc-2.95.2/newlib/libc/include -nostdinc -mbig-endian -DPACKAGE=\"newlib\ " -DVERSION=\"1.8.1\" -I. -I../../../../../../../../../gcc-2.95.2/newlib/newlib /libc/machine/i386 -I ../../../../../../../../../gcc-2.95.2/newlib/newlib/libc/ machine/i386/../../../libm/common -O2 -DMISSING_SYSCALL_NAMES -I./../../../targ- include -I./../../../../../../../../../gcc-2.95.2/newlib/newlib/libc/machine/i38 6/../../../libc/include -fno-builtin -g -O2 -mbig-endian -c ../../../../.. /../../../../gcc-2.95.2/newlib/newlib/libc/machine/i386/memchr.S ------snip----- where we see the remarkable sight of gcc trying to build newlib for a big endian x86! So it's gotten the wrong idea about paths, or configuration, somehow. Please send me *ALL* the output from the configure and build of gcc; I need more info. Please also send me the output you get when you do cd /home/Cristian/build-gcc/gcc ./xgcc -print-search-dirs ./xgcc -dumpmachine ./xgcc -print-file-name and in the meantime, there are two slight chances that might work: PATH=$PATH:$i This line from your bcr.sh might fix it if it actually said PATH=$i:$PATH If that doesn't work, there is a known problem of 2.95.2 that it needs the install directory $prefix/lib/gcc-lib/$target/$version to exist before building. You can try this by cd /home/Cristian/build-gcc/gcc/ make installdirs DaveK -- All your base are belong to us! ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |