RE: arm cross error

[David Korn <dkorn at pixelpower dot com>]

>-----Original Message-----
>From: pmcgarry [mailto:pmcgarry@hekimian.com]
>Sent: 16 March 2001 17:29


>>   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.

>Just FYI for everyone's benefit, I've used 1) and it works 
>like a champ!

  Thanks for the confirmation Pat.  I'll just point out that 2) has the
advantage that if you've gone halfway through a build and only realize
you've forgotten the headers when you see the "can't find stdlib.h /
unistd.h" errors, you can copy the target headers into the target include
dir and just start your 'make all' again, and it will pick up where it 
left off; this saves having to re-configure, clean, and rebuild.

  However 1) is indeed the 'officially approved' method and is a good way
to go when starting from scratch.

     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