This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Meir Hacohen wrote: > > Thanks for your help. I checked some things and now I got another error : > gcc -c -DIN_GCC -g -O2 -DHAVE_CONFIG_H -I. -I../../gcc-2.95.2/gcc > -I../../gcc-2.95.2/gcc/config -I../../gcc-2.95.2/gcc/../include Somehow the '-DCROSS_COMPILE' is not appearing here... So my bet is that something went wrong with your configure... This was seen already in your original message, but this case revealed the oddity... > ../../gcc-2.95.2/gcc/dbxout.c: In function `dbxout_start_new_source_file': > ../../gcc-2.95.2/gcc/dbxout.c:511: `N_BINCL' undeclared (first use in this > function) > ../../gcc-2.95.2/gcc/dbxout.c:523: `N_EINCL' undeclared (first use in this > function) > > I look for this variable - N_BINCL - in some places, and I really do not > find it. Can you help again ? These seem to be related to the stabs debug format. All cross-compilers should use the 'gstab.h' and the 'stab.def' it includes. The lines 170... in the 'dbxout.c' say: --------------------------- clip ------------------------------------- #if defined (USG) || !defined (HAVE_STAB_H) || defined (CROSS_COMPILE) #include "gstab.h" /* If doing DBX on sysV, use our own stab.h. */ #else #include <stab.h> --------------------------- clip ------------------------------------- If the 'CROSS_COMPILE' would be defined, as it should, there weren't problems with the N_BINCL and N_EINCL, because the 'stab.def' has them. So the configure command you used, seems to be the reason... Although you could just add the missing values (N_BINCL, N_EINCL) into your native '/usr/include/stab.h' (the values can be found in any BSD or Linux headers), doing a 'make distclean', reconfiguring and rebuilding is recommended. Your expected configure-command should be something like: ./configure --build=hppa1.1-hp-hpux10.20 --host=hppa1.1-hp-hpux10.20 \ --target=m68k-coff Ie. your build and host systems are the same, 'hppa1.1-hp-hpux10.20', and your target is 'm68k-coff'... Cheers, Kai ------ 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] |