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: 16 March 2001 06:53

>> >But now I have the following error:
>> >
>> >/gcc-2.95.2/gcc/config -I../../gcc-2.95.2/gcc/../include -c 
>> >-DL${name} \
>> >       ../../gcc-2.95.2/gcc/libgcc2.c -o ${name}.o; \
>> >  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
>> >  arm-coff-ar rc tmplibgcc2.a ${name}.o; \
>> >  rm -f ${name}.o; \
>> >done
>> >_muldi3
>> >../../gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file 
>or directory
>> >../../gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file 
>or directory
>> >make[3]: *** [libgcc2.a] Error 1
>>
>>  Yep.  This one is because you don't have any target header files.  Are
>>you planning on using newlib with this compiler?
>
>yeap

  Right.  In order to build libgcc.a for the target, the compiler needs to
have access to the header files for the target's runtime C library.  In
your case, that means the newlib header files.  There are several ways 
this can be done:

  1)  In the gcc-2.95.2 subdirectory, create a symbolic link called
'newlib' to the newlib source directory, and add the flag --with-newlib
to your configure command.

  2)  Copy the include header files from newlib to $prefix/$target/include.
In your case that would be /usr/local/arm-coff/include.

  3)  Add the option --with-headers=/path/to/newlib/headers to your
configure command.

  Of these options, 2) is probably the quickest and most sound.  I like
3) myself but I get told off by Kai Ruottu every time I suggest it, 
fortunately he's on holiday at the moment so I can get away with it.  1)
is meant to be an official solution to the problem as it kind-of
simulates doing a one-tree build but I haven't tried it myself.

  For further information about target headers, see 
http://gcc.gnu.org/onlinedocs/gcc_4.html#SEC63

     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]