This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: build failure, GMP not available
- From: Andrew Pinski <pinskia at gmail dot com>
- To: Geoffrey Keating <geoffk at apple dot com>
- Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, GCC Mailing List <gcc at gcc dot gnu dot org>, gcc-regression at gcc dot gnu dot org
- Date: Mon, 30 Oct 2006 10:02:26 -0800
- Subject: Re: build failure, GMP not available
- References: <76B13B3C-DB38-4D40-9DEE-B1ADC71379FC@apple.com>
On Mon, 2006-10-30 at 09:57 -0800, Geoffrey Keating wrote:
> Hi Kaveh,
>
> 1. Is this intentional?
Yes, do you read any of the mailing lists?
>
> 2. Is it supposed to apply to the host, the target, or both?
HOST.
>
> 3. If it's intentional, what is the list of platforms that you
> intended to prevent building, that is, platforms which GCC used to
> support but on which GMP or MPFR does not build?
NONE, except for i686-darwin but that is not Kaveh's fault, see below.
>
> 4. Are you aware that the GMP home page says
>
> [2006-05-04] GMP does not build on MacInteltosh machines. No fix
> planned for GMP 4.x.
>
> and indeed it does not appear to build correctly when configured on
> my MacBook Pro?
Make GMP build with the C sources only, they should have C sources and
if they don't, then it is a bug with them.
>
> 5. Are you aware that the GMP home page says
>
> Note that we chose not to work around all new GCC bugs in this
> release. Never forget to do make check after building the library
> to make likely it was not miscompiled!
>
> and therefore this library needs to be part of the bootstrap, not
> built separately?
Read the mailing list, it has already been mentioned there why.
> 6. The regression tester does actually have GMP installed, but it is,
> not in /usr/local. Should this code be searching for GMP and mpfr in
> more places if it is not found?
>
> Because of the severe nature of this problem (everything doesn't
> build, multiple hosts affected), I'd like you to consider backing out
> this patch until the problems are fixed. I'll work on a patch which
> just disables the check for Darwin.
You cannot because the build will be broken with or without the check
for GMP/MPRF because the middle-end uses it already.
Do you read the mailing list?
-- Pinski