> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of
> Joe Buck
> Sent: Monday, March 19, 2007 2:02 PM
> To: Andrew Pinski
> Cc: Florian Weimer; Steven Bosscher; gcc@gcc.gnu.org
> Subject: Re: Building mainline and 4.2 on Debian/amd6
Florian Weimer writes:
> Is there a convenient switch to make GCC bootstrap on Debian/amd64
> without patching the build infrastructure? Apparently, GCC tries to
> build 32-bit variants of all libraries (using -m32), but the new
> compiler uses the 64-bit libc instead of the 32-bit libc, hence
> b
Joe Buck writes:
>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.
The Debian-like AMD64 system I'm using ha
Florian Weimer wrote:
* Andrew Pinski:
Actually it brings up an even more important thing, distros that don't
include a 32bit user land is really just broken.
Are they? I haven't run into problems yet.
(And pretty please, I misread the documentation. It does *not* state
that amd64 is not
* Andrew Pinski:
> Actually it brings up an even more important thing, distros that don't
> include a 32bit user land is really just broken.
Are they? I haven't run into problems yet.
(And pretty please, I misread the documentation. It does *not* state
that amd64 is not a multilib target. Sor
Florian Weimer wrote:
* Steven Bosscher:
On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
I don't need the 32-bit libraries, so disabling their compilation
would be fine. --enable-targets at configure time might do the trick,
but I don't know what arguments are accepted.
Would --disable
On Mon, Mar 19, 2007 at 06:05:05PM +, Andrew Haley wrote:
> 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.
It does work. You have to do a bit more fiddling if you want to use
'make install' into a sys
Joe Buck writes:
> On Mon, Mar 19, 2007 at 10:35:15AM -0700, Andrew Pinski wrote:
> > On 3/19/07, Joe Buck <[EMAIL PROTECTED]> 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
> > >pres
On Mon, Mar 19, 2007 at 10:35:15AM -0700, Andrew Pinski wrote:
> On 3/19/07, Joe Buck <[EMAIL PROTECTED]> 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 d
On 3/19/07, Joe Buck <[EMAIL PROTECTED]> 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
On Mon, Mar 19, 2007 at 08:52:26AM +0100, Andreas Jaeger wrote:
> Florian Weimer <[EMAIL PROTECTED]> writes:
>
> > * Steven Bosscher:
> >
> >> On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
> >>> I don't need the 32-bit libraries, so disabling their compilation
> >>> would be fine. --enable
Florian Weimer <[EMAIL PROTECTED]> writes:
> * Steven Bosscher:
>
>> On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
>>> I don't need the 32-bit libraries, so disabling their compilation
>>> would be fine. --enable-targets at configure time might do the trick,
>>> but I don't know what argum
* Andrew Pinski:
> On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
>>
>> I'll try, but I doubt it. According to the installation
>> documentation, amd64 is not a multilib target.
>
> HUH??? Which documentation?
I misinterpreted the installation manual, sorry. I thought that all
the multil
On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
I'll try, but I doubt it. According to the installation
documentation, amd64 is not a multilib target.
HUH??? Which documentation? x86_64 for GCC is a multilib target and
has been since day 1 IIRC.
-- Pinski
* Steven Bosscher:
> On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
>> I don't need the 32-bit libraries, so disabling their compilation
>> would be fine. --enable-targets at configure time might do the trick,
>> but I don't know what arguments are accepted.
>
> Would --disable-multilib wor
On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
I don't need the 32-bit libraries, so disabling their compilation
would be fine. --enable-targets at configure time might do the trick,
but I don't know what arguments are accepted.
Would --disable-multilib work?
Gr.
Steven
Is there a convenient switch to make GCC bootstrap on Debian/amd64
without patching the build infrastructure? Apparently, GCC tries to
build 32-bit variants of all libraries (using -m32), but the new
compiler uses the 64-bit libc instead of the 32-bit libc, hence
building them fails.
I don't need
17 matches
Mail list logo
