On Mon, Jul 8, 2013 at 12:19 AM, Andrew Pinski <pins...@gmail.com> wrote: > On Sun, Jul 7, 2013 at 10:17 PM, Gabriel Dos Reis > <g...@integrable-solutions.net> wrote: >> On Sun, Jul 7, 2013 at 6:02 PM, Jonathan Wakely <jwakely....@gmail.com> >> wrote: >>> On 7 July 2013 21:33, Gabriel Dos Reis wrote: >>>> How about not enabling multi lib build by default on targets we now that >>>> will fail anyway? I have the suspicion this problem is unique to openSUSE, >>>> so we can take care of that. >>> >>> I'm pretty sure I've seen it happen with RHEL and Fedora, and Ubuntu >>> users have asked about the same thing on the gcc-help list. >> >> Ha, if it is that spread then we might have even more reasons to >> have it work more generally, for example, by disabling multilib by default. >> I think the situation we are in now is very different from the situation >> we were in more than a decade ago. > > 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.
Why do you think it is a broken choice? Personally, I don't see anything broken with that. The world we are in today is very different from a decade ago. More than a decade ago, a multilib build by default -probably- made sense; I don't see that today. -- Gaby
