All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386 -> x86_64 cross compile failure (binutils bug?)
Date: Sat, 10 Dec 2005 15:48:23 -0500	[thread overview]
Message-ID: <1134247704.18432.119.camel@mindpipe> (raw)
In-Reply-To: <1134246859.5192.1.camel@bip.parateam.prv>

On Sat, 2005-12-10 at 21:34 +0100, Xavier Bestel wrote:
> Le vendredi 09 décembre 2005 à 20:31 -0500, Lee Revell a écrit :
> > On Fri, 2005-12-09 at 23:43 +0100, Xavier Bestel wrote:
> > > Le vendredi 09 décembre 2005 à 13:50 -0500, Lee Revell a écrit :
> > > > I'm trying to build an x66-64 kernel on a 32 bit system (Ubuntu 5.10).
> > > > I added -m64 to the CFLAGS as per the gcc docs. 
> > > 
> > > Under debian 32bits with 64bits kernel, I just add -m64 somewhere in the
> > > main Makefile to rebuild my modules. Didn't try with a whole kernel
> > > though.
> > 
> > The bug seems to be that the kernel build system does not grok biarch
> > toolchains - it really insists on a separate toolchain for i386 and
> > x86_64 even though the situation can be handled with selective use of
> > -m64.  If I jsut add -m64 to everything then it fails when it gets to
> > the ia32 stuff.
> 
> Yes, you shouldn't compile host executables with -m64, obviously.
> 
> --- /usr/src/linux-headers-2.6.14-2/Makefile.old        2005-12-10 21:32:17.000000000 +0100
> +++ /usr/src/linux-headers-2.6.14-2/Makefile    2005-11-17 14:26:02.000000000 +0100
> @@ -352,7 +352,7 @@
> 
>  CFLAGS                 := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
>                    -fno-strict-aliasing -fno-common \
> -                  -ffreestanding
> +                  -ffreestanding -m64
>  AFLAGS         := -D__ASSEMBLY__
> 
>  export VERSION PATCHLEVEL SUBLEVEL EXTRAVERSION LOCALVERSION KERNELRELEASE \
> 
> 
> HTH,

This would break native 32 bit kernel builds.  Andi's patch seems to be
the correct solution.

Lee


      reply	other threads:[~2005-12-10 20:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 18:50 i386 -> x86_64 cross compile failure (binutils bug?) Lee Revell
2005-12-09 19:50 ` Ken Moffat
2005-12-09 19:59   ` Lee Revell
2005-12-09 21:30     ` Ken Moffat
2005-12-09 21:40       ` Lee Revell
2005-12-09 22:19         ` Ken Moffat
2005-12-09 19:58 ` Kyle McMartin
2005-12-09 20:21   ` Lee Revell
2005-12-09 20:41     ` Kyle McMartin
2005-12-09 20:58       ` Lee Revell
2005-12-09 21:25         ` Steven Rostedt
2005-12-09 21:35           ` Lee Revell
2005-12-09 21:10       ` Lee Revell
2005-12-09 21:19         ` Kyle McMartin
2005-12-09 22:37 ` Jeffrey Hundstad
2005-12-10  0:05   ` Lee Revell
2005-12-10  0:23     ` Jeffrey Hundstad
2005-12-10  1:28       ` Lee Revell
2005-12-10  1:50       ` Lee Revell
2005-12-10  8:56         ` Andi Kleen
2005-12-10  5:12           ` Lee Revell
2005-12-10  7:19             ` Andi Kleen
2005-12-10  7:43               ` Lee Revell
2005-12-10 19:34               ` Lee Revell
2005-12-11  0:00                 ` Andi Kleen
2005-12-11  0:26                   ` Lee Revell
2005-12-16 23:40                   ` Lee Revell
2005-12-23  5:59                   ` Lee Revell
2006-01-11 16:48                   ` Lee Revell
2006-01-11 16:54                     ` Andi Kleen
2005-12-09 22:43 ` Xavier Bestel
2005-12-10  1:31   ` Lee Revell
2005-12-10 20:34     ` Xavier Bestel
2005-12-10 20:48       ` Lee Revell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1134247704.18432.119.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.