This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: 64-bit configure hell
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- To: Ulrich Weigand <Ulrich dot Weigand at de dot ibm dot com>
- Cc: bkoz at redhat dot com, gcc at gcc dot gnu dot org, shebs at apple dot com
- Date: 25 Nov 2004 21:38:28 +0100
- Subject: Re: 64-bit configure hell
- References: <OF7EB3AD39.A3ED768D-ON41256F57.005E97CD-41256F57.0063FB13@de.ibm.com>
Ulrich Weigand <Ulrich.Weigand@de.ibm.com> writes:
> I guess one way to fix this problem would be to only build those
> multilibs where the required system dependencies are in fact installed;
> this could be verified by attempting to build a 'hello world' using
> the multilib flags. If this already fails, there's no point in
> attempting to build the library.
>
> Something like that is actually attempted in config-ml.in, at least
> for some platforms. However this doesn't work, as those checks are
> not applied for libgcc (and thus we fail already there). I think I
> pointed this out already some time in the past, and was told that
> this is difficult to fix with the current make process ...
Indeed: libgcc would have to be moved to the toplevel, since you need the
stage 1 compiler to perform this test. The bootstrap compiler may not be
gcc (so require multilib flags different from gcc's) or not be
multilib-aware.
Rainer