Building mainline and 4.2 on Debian/amd64
Andrew Haley
aph@redhat.com
Mon Mar 19 18:05:00 GMT 2007
Joe Buck writes:
> On Mon, Mar 19, 2007 at 10:35:15AM -0700, Andrew Pinski wrote:
> > On 3/19/07, Joe Buck <Joe.Buck@synopsys.com> wrote:
> > >This brings up a point: the build procedure doesn't work by default on
> > >Debian-like amd64 distros, because they lack 32-bit support (which is
> > >present on Red Hat/Fedora/SuSE/etc distros). Ideally this would be
> > >detected when configuring.
> >
> > Actually it brings up an even more important thing, distros that don't
> > include a 32bit user land is really just broken. Why do these distros
> > even try to get away with this, they are useless to 99.9% of the
> > people and for the 0.1% of the people who find them interesting, they
> > can just compile with --disable-multilib.
>
> Unfortunately, such distros are in common use, and the GCC project jumps
> through hoops to support many things that get far less use.
>
> A platform that contains only 64-bit libraries is fundamentally a
> different platform than one that has both 32- and 64-. Ideally there
> would be a different target triplet for such platforms. Maybe
> x86_64only? But that would have to be handled upstream.
>
> In the meantime, the installation instructions should tell people to
> use --disable-multilib.
Will that work? Unless there's some more configury I don't
understand, they'll still end up with libraries in /lib64 rather than
/lib.
Andrew.
More information about the Gcc
mailing list