Bugzilla Bug 213687

OK, I know it's still masked yet, but I thought I'd try gcc-4.3.0.  Based on
the following error, it seems to have a missing depend on
>=dev-libs/mpfr-2.3.0.  Shortly into the initial config checking, it fails with
the below:

checking for correct version of gmp.h... yes
checking for correct version of mpfr.h... no
configure: error: Building GCC requires GMP 4.1+ and MPFR 2.3.0+.
Try the --with-gmp and/or --with-mpfr options to specify their locations.
Copies of these libraries' source code can be found at their respective
hosting sites as well as at ftp://gcc.gnu.org/pub/gcc/infrastructure/.
See also http://gcc.gnu.org/install/prerequisites.html for additional info.
If you obtained GMP and/or MPFR from a vendor distribution package, make
sure that you have installed both the libraries and the header files.
They may be located in separate packages.


I didn't have mpfr merged as nothing so far has depended on it, but just merged
mpfr-2.3.1 manually and the gcc-4.3.0 merge has already proceeded well beyond
the previous failure point.

Emerge info can be attached if needed, but meanwhile, ~amd64 no-multilib, with
package.keywords set to grab binutils and gcc as **, since I like testing,
Gentoo makes switching between versions if one fails so easy, and I have
FEATURES=buildpkg backups if the build system gets totally hosed. =8^)

Here's the USE flags as emerge -pv gcc spits them out:

[ebuild  NS   ] sys-devel/gcc-4.3.0  USE="mudflap openmp (-altivec) -bootstrap
-build -doc -fortran -gcj -gtk (-hardened) -ip28 -ip32r10k -libffi (-multilib)
-multislot (-n32) (-n64) -nls -nocxx -objc -objc++ -objc-gc -test -vanilla"

Duncan

FWIW, with mpfr merged, gcc-4.3.0 merged fine, and I'm now doing an emerge
system.  No (other) problems so far, altho I'd read how much stricter 4.3 was,
so kudos to the Gentoo toolchain folks. =8^)

Also, read the upstream gcc-4.3.0 announcement and changes (checking to see if
I might want to change my CFLAGS/CXXFLAGS =8^), and the mpfr requirement is
pretty close to the top of the list of changes, so it's officially needed.  I'm
not sure why the ebuild didn't have it in the deps.

Duncan

gcc-4.3 ebuild has mpfr dependency, but only for fortran. I don't know why :/.

fortran? (
    >=dev-libs/gmp-4.2.1
    >=dev-libs/mpfr-2.2.0_p10
)

(In reply to comment #2)
> gcc-4.3 ebuild has mpfr dependency, but only for fortran.

> fortran? (
>     >=dev-libs/gmp-4.2.1
>     >=dev-libs/mpfr-2.2.0_p10
> )

Thanks for noting that.  As you may have noted from my USE above, I don't have
fortran enabled, so didn't look there and missed it.

Even then however the dependency is outdated, as gcc now requires mpfr 2.3+,
according to the error as I posted and according to the announcement, as well
as requiring it for C-family as well as fortran.  So I'd guess that's probably
a stale depend from earlier versions, and they simply missed the newer depend.

(As the error states, there's a gmp dependency as well, but I apparently have
it from something else.)

we've had this fix in our overlay for a long time, it was just missed when
updating the tree

as for depending on gfortran that's obvious: older versions of gcc only needed
gmp/mpfr when building the gfortran code, but gcc-4.3 uses both pieces in the
normal compiler as well