Subject: Re: i386 -> x86_64 cross compile failure (binutils bug?)
From: Lee Revell <rlrevell@joe-job.com>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <1134168222.5270.1.camel@bip.parateam.prv>
References: <1134154208.14363.8.camel@mindpipe>
	 <1134168222.5270.1.camel@bip.parateam.prv>
Content-Type: text/plain; charset=ISO-8859-1
Date: Fri, 09 Dec 2005 20:31:19 -0500
Message-Id: <1134178279.18432.55.camel@mindpipe>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 954
Lines: 22

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.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/