Re: Building newlib without -mhard-float

[Rick Mann <rmann at latencyzero dot com>]

On Sep 5, 2007, at 4:10 PM, Ralf Corsepius wrote:

> Ewww, ... - We are doing for so long, I don't recall if there were or
> are any directions :)
>
>
> In a nutshell, it's:
>
> tar xjvf gcc-<gccversion>.tar.bz2
> tar xzvr newlib-<newlibversion>.tar.gz
> ln -s ../newlib-<newlibversion>/newlib gcc-<gccversion>
>
> mkdir BUILD
> cd BUILD
> ../gcc-<gccversion>/configure --with-newlib .....
>
> i.e. symlink newlib-<version>/newlib into the gcc source tree and then
> use gcc's configure (it knows about newlib)

Thanks. I'm in the middle of it now, but one thing that's not clear  
is: do I need to also configure and make newlib, after "make install- 
gcc"? Okay, I checked, and it didn't get installed.

Here's the question, then: do I make newlib in the same build dir as  
gcc, or in a separate one?

TIA

> For details (and should you be familiar with rpm specs), cf.
> http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems/contrib/crossrpms/ 
> rtems4.8/arm/rtems-4.8-arm-rtems4.8-gcc.spec

I don't know RPM specs, but I'll try to figure it out.

Thanks!

--
Rick