Re: help about cross-compiler

[Kai Ruottu <kai dot ruottu at luukku dot com>]

On Mon, 09 Jul 2001 09:38:21 +0800
"Liu Yong" <yliu@newavetech.com> wrote:

> gcc : 3.0

 What about using a more stable GCC like gcc-2.95.3 ?

> /my-gcc/vi configure(change the target(m68k-hp-bsd4.3 and prefix director 
> 
> So what 's wrong with my Gcc?
> Do you think I need libgcc1.a? I have no this files.

 You should have more info about the target than we have...

 The 'libgcc1.a' normally has the 'soft-float' routines for m68020 etc.
without a m68881/m68882 FPU. If your target always has the FPU, the
'soft-float' routines and the '-msoft-float' option may be vain. The
main config file ('gcc/config/m68k/hp3bsd.h') says the '-m68020' and
'-m68881' being the defaults... So the compiling the 'fpgnulib.c' and
the 'xfgnulib.c' into 'libgcc1.a' may be unnecessary...

 Also the conversion routines in 'gcc/config/m68k/lb1sf68.asm' may be
unnecessary...

 So defining 'LIBGCC1 = libgcc1.null' in your '$build_dir/gcc/Makefile'
(after "target overrides"), or defining it as empty, will cause no
'libgcc1.a' to be produced...

> Because I have no computer based on m68k ,I cann't generate it.

 How on earth you are going to test the produced executables then?
You probably don't need a cross-compiler for an unexisting target ;-)

> > Maybe I should install glibc? I haven't installed it.

 You should copy the target headers and libs from the target machine
into your host machine, please read the "Installation / Cross-Compiler"
from your nice GCC-manual ("Using and Porting the GNU Compiler Collection").

 If you don't have the manual (comes with GCC sources in 'texinfo' format)
built yet, please build it now... The 'makeinfo' which produces the 'info'
format manual, should come with the GCC-sources. With TeX a '.dvi' document
can be produced, with Ghostscript a '.ps' one. Or you can download a prebuilt
manual from the net, like from the RedHat's 'GNUPro Toolkit Documentation'
site...

 Maybe the 'glibc-1.09' can be built for 'm68k-hp-bsd4.3' and it works somehow,
but the original BSD4.3-libraries are much better and the target system should
have them.

 Anyway the 'include' and 'lib' under the $prefix/$target are the places for
the target headers and libraries, just as the 'bin' there should now be filled
with the target binutils.

 The :

  -B/home/yliu/local/m68k-hp-bsd4.3/lib/ \
  -isystem /home/yliu/local/m68k-hp-bsd4.3/include

in your earlier message tells your $prefix being '/home/yliu/local' and the
$target being 'm68k-hp-bsd4.3', so this output log from you clearly shows
the places for the target libs ('lib') and the headers ('include'). Your
target binutils should be in '/home/yliu/local/m68k-hp-bsd4.3/bin' now, the
new 'xgcc' tries to find them there (please see this with the well-known
'./xgcc -print-search-dirs').

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