From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: CROSS_COMPILE in environment variable
Date: Tue, 25 Apr 2006 11:32:46 -0700 [thread overview]
Message-ID: <444E6B4E.5000608@am.sony.com> (raw)
In-Reply-To: <20060425.133944.88701465.nemoto@toshiba-tops.co.jp>
Atsushi Nemoto wrote:
> In the toplevel Makefile, CROSS_COMPILE is described as:
>
> # CROSS_COMPILE can be set on the command line
> # make CROSS_COMPILE=ia64-linux-
> # Alternatively CROSS_COMPILE can be set in the environment.
> # Default value for CROSS_COMPILE is not to prefix executables
> # Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
>
> And currently, arch/mips/Makefile assigns CROSS_COMPILE as:
>
> CROSS_COMPILE := $(tool-prefix)
>
> This overrides environment variable's settings unconditionaly so we
> can no do the 'alternative' method described above (specify
> CROSS_COMPILE by shell environment variable).
>
> If arch/mips/Makefile used "?=" assigment instead of ":=", we can
> specify CROSS_COMPILE by shell environment variable.
>
> Is there any reason to using ":=" ? If no, shouldn't we change
> arch/mips/Makefile corresponding to the description?
>
In general this seems correct.
Another point is that the kernel has this:
ifdef CONFIG_CROSSCOMPILE
CROSS_COMPILE := $(tool-prefix)
endif
config CROSSCOMPILE
bool "Are you using a crosscompiler"
help
Say Y here if you are compiling the kernel on a different
architecture than the one it is intended to run on.
I think the Kconfig could be changed to say that CONFIG_CROSSCOMPILE
makes the build system use a built-in default tool prefix.
-Geoff
next prev parent reply other threads:[~2006-04-25 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 4:39 CROSS_COMPILE in environment variable Atsushi Nemoto
2006-04-25 18:32 ` Geoff Levand [this message]
2006-04-26 1:36 ` Atsushi Nemoto
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=444E6B4E.5000608@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox