Hi, On Sun, Jul 7, 2013 at 10:19 PM, Andrew Pinski <pins...@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.
