From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Finn Thain <fthain@telegraphics.com.au>,
LKML <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] Make m68k cross compile like every other architecture.
Date: Mon, 15 Oct 2007 19:31:54 -0500 [thread overview]
Message-ID: <200710151931.54289.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0710152217150.16889@anakin>
On Monday 15 October 2007 3:25:35 pm Geert Uytterhoeven wrote:
> 64-bit parisc tests if /usr/bin/hppa64-linux-gnu- exists.
> If yes, it sets CROSS_COMPILE to hppa64-linux-gnu-.
> If no, it sets CROSS_COMPILE to hppa64-linux-
>
> 32-bit parisc unconditionally sets CROSS_COMPILE to hppa-linux-.
>
> This still breaks Rob's setup if his compiler is called differently.
Another thing to take into account is that kconfig was recently changed to
save ARCH and CROSS_COMPILE in the .config file:
http://lwn.net/Articles/253889/
Presumably that means you'd only have to specify your arch and cross compiler
during config, and then if you re-used that config it would re-use those
settings. But the existing makefile discards anything that isn't explicitly
overridden on the make command line at each stage of the build.
It seems to me any fix should only reset CROSS_COMPILE if there isn't already
a value for it. (Otherwise there's a potentially subtle bug where a year
from now you might have "m68k-linux-gnu-gcc" and "m68k-linux-gnu-pcc" and
want to compare the results of building with the different compilers.)
I still lean towards considering any attempt to cross compile without setting
CROSS_COMPILE an error, and not guessing at what the user meant. But perhaps
that's just personal preference...
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-10-16 0:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 22:22 [PATCH] Make m68k cross compile like every other architecture Rob Landley
2007-10-11 7:25 ` Geert Uytterhoeven
2007-10-11 11:31 ` Rob Landley
2007-10-11 11:39 ` Sam Ravnborg
2007-10-11 12:46 ` Geert Uytterhoeven
2007-10-11 13:27 ` Rob Landley
2007-10-11 13:52 ` Paul Mundt
2007-10-11 15:12 ` Geert Uytterhoeven
2007-10-11 16:26 ` Finn Thain
2007-10-11 21:14 ` Rob Landley
2007-10-12 6:51 ` Geert Uytterhoeven
2007-10-12 7:54 ` Finn Thain
2007-10-12 8:51 ` Geert Uytterhoeven
2007-10-12 10:21 ` Sam Ravnborg
2007-10-15 20:25 ` Geert Uytterhoeven
2007-10-16 0:31 ` Rob Landley [this message]
2007-10-16 4:15 ` Sam Ravnborg
2007-10-18 21:14 ` Sam Ravnborg
2007-10-19 6:38 ` Rob Landley
2007-10-19 15:10 ` Sam Ravnborg
2007-10-11 16:24 ` Sam Ravnborg
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=200710151931.54289.rob@landley.net \
--to=rob@landley.net \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.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