linux-kernel - Re: [PATCH] Make m68k cross compile like every other architecture.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0710111443530.3729@anakin>
Date:	Thu, 11 Oct 2007 14:46:47 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Rob Landley <rob@...dley.net>, LKML <linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...r.kernel.org>
Subject: Re: [PATCH] Make m68k cross compile like every other architecture.

On Thu, 11 Oct 2007, Sam Ravnborg wrote:
> On Thu, Oct 11, 2007 at 09:25:19AM +0200, Geert Uytterhoeven wrote:
> > On Wed, 10 Oct 2007, Rob Landley wrote:
> > > From: Rob Landley <rob@...dley.net>
> > > 
> > > Rip out hardwired cross compiler name assumption that only m68k makes.
> > > 
> > > Signed-off-by: Rob Landley <rob@...dley.net>
> > > ---
> > > 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-
> > 
> > BTW, m68k-linux-gnu- is the default name for a m68k cross compiler.
> 
> For "make headers_install" this is not good.
> But I see there is confliting usages here.
> 1) current functionality makes it easy to build a cross compiled m68k
> 
> Btw. if you did:
> CROSS_COMPILE ?= m68k-linux-
> 
> then I could do:
> export CROSS_COMPILE=my-m68k-linux-
> make
> 
> and still get the expected result.

That won't work, cfr. http://lkml.org/lkml/2007/5/6/58.

> 2) suggested functionality makes it easy to do make headers_install

This is something completely different (cfr. the other thread handling
it). If `make headers_install' doesn't need the cross compiler, it
should not try to execute it.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/