On Thursday 11 October 2007 2:25:19 am Geert Uytterhoeven wrote:
On Wed, 10 Oct 2007, Rob Landley wrote:
From: Rob Landley <rob@xxxxxxxxxxx>
Rip out hardwired cross compiler name assumption that only m68k makes.
Signed-off-by: Rob Landley <rob@xxxxxxxxxxx>
---
When you cross compile, you have to set the prefix CROSS_COMPILE to your
cross compiler prefix. You need to do this for all targets (arm, mips,
ppc, x86-64 on x86, etc). This is not specific to m68k, and this value
is supplied _to_ the build, not supplied _by_ the build.
The build shouldn't unconditionally overwrite the existing value of this
variable with one it makes up. It has no idea what I called my cross
compiler.
The build does not unconditionally overwrite the existing value of this
variable. You can specify the name of your cross compiler like this:
make CROSS_COMPILE=m68k-linux-
I noticed this because you have to specify ARCH for "make headers_install" but
don't have to specify a CROSS_COMPILE prefix for that because it doesn't
build anything. Yet the first line it spits out is a complaint that it can't
find m68k-linux-gnu-gcc.
I do note that the error message doesn't stop the build, and seems to be
ignored...
BTW, m68k-linux-gnu- is the default name for a m68k cross compiler.
*shrug* This is the eleventh target I've tried to build, and the first one
that has this behavior. It seemed unnecessary at best.
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
-
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
