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]

RE: arm cross error



>-----Original Message-----
>From: Cristian Amitroaie [mailto:Cristian.Amitroaie@nobugconsulting.ro]
>Sent: 19 March 2001 08:35

>Thnx for help, but it seems I don't have luck. It is the first time I try 
>to make a cross and the errors are all over me.

  Most people have troubles the first time they learn how to make a 
cross compiler.  Once you've done it once, it gets easier!

>Despite the fact that I do exactly what is written in "CrossGCC Frequently
>Asked Questions" ->chapter 4 "How to configure, build and install GCC as a 
>cross-compiler" ->section 4.1 "Unix Systems from 
>http://www.objsw.com/CrossGCC/ it seems :

  The CrossGCC FAQ, although it is good in many ways, is sadly out-of-
date.  In particular, it doesn't mention the need for target headers.  It
is also just plain wrong about the build process when using newlib.

>in/ -I. -I../../../gcc-2.95.2/libio -nostdinc++ -nostdinc++ -g 
>-O2"; export
>CXX;
> \
>CONFIG_NM="arm-coff-nm"; export CONFIG_NM; \
>/bin/sh ../../../gcc-2.95.2/libio/gen-params LIB_VERSION=2.8.0
>>tmp-params.h
>dummy.c:1: sys/types.h: No such file or directory
>dummy.c:8: stdio.h: No such file or directory
>dummy.c:9: time.h: No such file or directory
>dummy.c:10: signal.h: No such file or directory
>gen-params: could not invoke
>/home/Cristian/b-gcc/gcc/xgcc -B/home/Cristian/b-gc
>c/gcc/ -B/bar/arm-coff/bin/ -I. -I../../../gcc-2.95.2/libio -E 
>on dummy.c
>make[1]: *** [_G_config.h] Error 1
>make[1]: Leaving directory `/home/Cristian/b-gcc/arm-coff/libio'
>make: *** [all-target-libio] Error 2

  Hmm.  I think this may be related to the fact that the Cross GCC FAQ
says you must build and install gcc before newlib.  That might have worked
back in 2.8.1 days, but not any more.  What you have to do is

 - configure gcc using the "--enable-languages=c" option

 - "make LANGUAGES=c all install" for gcc.  This installs the c compiler 
only, but as long as you followed the advice in my previous email of
16/Mar/01, 16:30 GMT, it should also install the newlib headers

 - now configure newlib, and do "make all install" for it.

 - now re-configure Gcc, but with "--enable-languages=c,c++" (or with no
enable-langs option at all if you want the fortran, chill, java compilers
to also be built).
 
 - finally "make all install" for gcc once more.


     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]