From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lukasz Majewski <l.majewski@majess.pl>
Date: Tue, 18 Mar 2014 23:09:39 +0100
Subject: [U-Boot] [PATCH] build:arm: Remove setting of CROSS_COMPILE
 environment variable
In-Reply-To: <20140318162248.GC16360@bill-the-cat>
References: <1395157608-18834-1-git-send-email-l.majewski@samsung.com>
	<20140318162248.GC16360@bill-the-cat>
Message-ID: <20140318230939.62536707@jawa>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Tom,

> On Tue, Mar 18, 2014 at 04:46:48PM +0100, Lukasz Majewski wrote:
> 
> > After Kbuild introduction, the CROSS_COMPILE environment variable
> > has been set to some default value (prefix arm-linux-).
> 
> Note that this is quite a long-standing thing.  Perhaps we're now not
> detecting a native build when we used to?

My point is that we are relying on assigning default prefix (i.e.
arm-linux-)

For example OSELAS toolchains can have an arbitrary prefix
(e.g. arm-linux-gnueabi-).

When I cross compile I set explicitly "CROSS_COMPILE=<toolchain> make"
and it works as it should (with or without this patch). Such approach
seems natural for me.

However, I don't know what is the exact rationale for seting this
arm-linux- prefix to CROSS_COMPILE.
I can only guess, that it is connected with situation when one just
type "make" on x86_64 host and expect u-boot to be CROSS_COMPILE'd
out of the box.

Unfortunately this doesn't work with ARM host emulated with qemu (like
OBS). Here when I type "make" I expect that "native" gcc for arm will
run without even touching CROSS_COMPILE environment variable.

Any idea how to fix this is more than welcome.

Best regards,
Lukasz Majewski



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140318/a89c0703/attachment.pgp>