RFC: cutting 4.9.0 on 24 September

[Ralf Corsepius]

On Sun, 2008-09-21 at 10:33 -0400, Jerry Needell wrote:
> I am "trying" to test the 4-9 branch, but I am having trouble building 
> some of the tools.
> In particular, gcc-4.3.2 complained ta\hat it needed mpfr so I built 
> mpfr and added a link to it in the gcc-4.3.2 source tree.
Building GCC-4.3.x requires mpfr installed 
OR 
to build it when building GCC.

> It then configured, but the build fails with:
> 
> Checking multilib configuration for libgcc...
> mkdir -p -- sparc-rtems/libgcc
> Configuring in sparc-rtems/libgcc
> configure: creating cache ./config.cache
> checking for --enable-version-specific-runtime-libs... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for gawk... gawk
> checking build system type... i686-pc-linux-gnu
> checking host system type... sparc-unknown-rtems
> checking for sparc-rtems-ar... sparc-rtems-ar
> checking for sparc-rtems-lipo... sparc-rtems-lipo
> checking for sparc-rtems-nm... /home/needell/leon/rtems/b-gcc/./gcc/nm
> checking for sparc-rtems-ranlib... sparc-rtems-ranlib
> checking for sparc-rtems-strip... sparc-rtems-strip
> checking whether ln -s works... yes
> checking for sparc-rtems-gcc... 
> /home/needell/leon/rtems/b-gcc/./gcc/xgcc 
> -B/home/needell/leon/rtems/b-gcc/./gcc/ -B/opt/rtems/sparc-rtems/bin/ 
> -B/opt/rtems/sparc-rtems/lib/ -isystem /opt/rtems/sparc-rtems/include 
> -isystem /opt/rtems/sparc-rtems/sys-include
> checking for suffix of object files... configure: error: cannot compute 
> suffix of object files: cannot compile
> See `config.log' for more details.
> make[1]: *** [configure-target-libgcc] Error 1
> make[1]: Leaving directory `/home/needell/leon/rtems/b-gcc'
> make: *** [all] Error 2
> 
> 
> 
> 
> Any suggestions of what is going on?
> Would someone alo please comment on the proper way to build and install 
> mpfr as part of the tool chain.

All modern Linuxes ship mpfr =>  Installing the mpfr-development package
your vendor ships (Called mpfr-devel, libmpfr-devel, mpfr-dev or
similar) should be sufficient - You don't have to build it.


Building mpfr as part of the toolchains is only necessary if your vendor
ships an insufficient version of mpfr (e.g. SuSE < 11.0, older
RHEL/CentOS) or doesn't ship mpfr at all.

In these cases, mpfr can built during the toolchain-built, by adding a
symlink from mpfr into the gcc source tree 

tar xjf gcc-core-4.3.2.tar.bz2
tar xjf gcc-g++-4.3.2.tar.bz2
tar xjf mpfr-<mpfr-version>.tar.
ln -s ../mpfr-<mpfr-version> gcc-4.3.2/mpfr


Alternative: Separately build and install mpfr.


My recommendation: If possible, use vendor supplied mpfr packages.

Ralf