This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: fatal error: gnu/stubs-32.h: No such file
- From: Bruce Korb <bruce dot korb at gmail dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, Jonathan Wakely <jwakely dot gcc at gmail dot com>, Andreas Schwab <schwab at linux-m68k dot org>, GCC <gcc at gcc dot gnu dot org>
- Date: Mon, 8 Jul 2013 08:11:03 -0700
- Subject: Re: fatal error: gnu/stubs-32.h: No such file
- References: <51D83AAC dot 4080200 at gmail dot com> <87y59jo6yq dot fsf at igel dot home> <51D97472 dot 8010704 at gmail dot com> <CAH6eHdSzVcjpVzktBfi6n0cNq=DfBOADAP3BpvTqydmzCFwbCQ at mail dot gmail dot com> <CAAiZkiB0W3Lbv63eXcpP6EYhbj-t4DJ=zvFEsSfer_n6nKM_wA at mail dot gmail dot com> <CAH6eHdS9v+GyLvVYEjVDbuFtGxwn27-VhqEofykYMe0C_tv9aA at mail dot gmail dot com> <CAAiZkiBjh3iR+Gsh2etKRnzO2q=N5iBnXQgwwod4vOELSsbLRA at mail dot gmail dot com> <CA+=Sn1=M9_uUHxEV6r0b-0AQE73v=Lv=AgbWwT9nAMuZ=_M7xQ at mail dot gmail dot com>
Hi,
On Sun, Jul 7, 2013 at 10:19 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> I think disable multilib by default is a mistake and is a broken
> choice for broken distros which don't install the 32bit development by
> default when you install the development part.
If a distro does something that you consider wrong, you would have their many
clients suffer? When there's a simple test to see if the platform can support
multilib? That is not very friendly. Not friendly at all.
> > I think the problem is still in the distros rather than GCC.
>
> I strongly disagree. We (GCC) are at fault here. We implicitly
> enable a feature at configure time without knowing its builds
> will succeed (despite having repeated reports that it does often
> fail) without much input from the builder (who might be ignorant of
> real reason of failures.) Usually we do the opposite.
Making the innocent suffer inscrutible failures because you think that many
mass distributions are wrong? That is wrong. I agree whole heartedly with
Gaby.
> But having multilib enabled by default on x86_64 is simply very highly
> desirable,
REMEMBER: we are talking about having a multilib enableable test in
the configure. If it fails, then it is not enabled by default. This is not
rocket science.
> If you don't have gmp or mfr installed,
> configure will let you know, loudly complains, and won't budge until
> you install the required tools
Exactly.
> > It's better to abort early.
>
> it is, as the saying goes, drowning the baby because we want to
> keep the water.
:-D It is punishing the innocent by failing the build with inscrutible
error messages. Sounds like baby drowning to me...
Please add a multilib-able test to configure. Thank you.