problem installing gcc 2.95.2 on m68k-coff

Meir Hacohen meir.hacohen@telrad.co.il
Thu Oct 26 06:24:00 GMT 2000


Hello,

  I tried to install gcc cross compilers, and that is what I got :

1. When I work with target m68k-aout I use the command :

../gcc-2.95.2/configure --build=hppa1.1-hp-hpux10.20 --host=hppa1.1-hp-hpux10.20 --target=m68k-aout
--with-headers=/gnu/newlib-1.8.2

and the configure works fine.

But after the make command I got at the end :

_mulsi3
as: unrecognized option `-mc68020'
make[1]: *** [libgcc1-asm.a] Error 1
make[1]: Leaving directory `/gnu/gcc-obj/gcc'
make: *** [all-gcc] Error 2


2. When I work with target m68k-coff I use the command :

../gcc-2.95.2/configure --build=hppa1.1-hp-hpux10.20
--host=hppa1.1-hp-hpux10.2$ --target=m68k-coff 
--with-headers=/gnu/newlib-1.8.2
  
and the configure works fine.

But after the make command I got at the end :

make[2]: Entering directory `/gnu/gcc-obj/m68k-coff/libiberty'
make[2]: *** No targets.  Stop.
make[2]: Leaving directory `/gnu/gcc-obj/m68k-coff/libiberty'
make[1]: *** [../libiberty/libiberty.a] Error 2
make[1]: Leaving directory `/gnu/gcc-obj/m68k-coff/libstdc++'
make: *** [all-target-libstdc++] Error 2


Can someone tell me what is the meaning of those errors , and how can I fix
them ?

Regards,

Meir

*******************************************************************************
Meir     Hacohen                         Tel    :           +972-8-9133394
PLS-DMS-SIR team                         Fax    :           +972-8-9133264
Telrad,   Israel                         e-mail: meir.hacohen@telrad.co.il
P.O.B. 50,   Lod                         ESN    :                 828-3394   
*******************************************************************************


On Mon, 25 Sep 2000, Kai Ruottu wrote:

> 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



More information about the crossgcc mailing list