(catching up on old email) On Jul 8, 2013, Gabriel Dos Reis <g...@integrable-solutions.net> wrote:
> 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 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. Heh. Back in 1999, I had a patch accepted that disabled the 64-bit multilibs on mips*-*-* if we couldn't link a trivial program due to missing 64-bit libraries on an IRIX5 box I used to have access to for GCC testing back then. It is a very different world indeed: now it's the 32-bit libs that are frequently not available ;-) trunk rev 26355, git commit a48ef8ee5c527137faa2aec5b9101ad63d41fbd6, if anyone's interested. FWIW, that patch was removed at a later point, for reasons I no longer recall. It surely didn't meet all the requirements mentioned in this thread. -- Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ You must be the change you wish to see in the world. -- Gandhi Be Free! -- http://FSFLA.org/ FSF Latin America board member Free Software Evangelist Red Hat Brazil Compiler Engineer
