mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Rob Landley <rob@landley.net>,
	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: Thu, 11 Oct 2007 14:46:47 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710111443530.3729@anakin> (raw)
In-Reply-To: <20071011113931.GB8393@uranus.ravnborg.org>

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@landley.net>
> > > 
> > > Rip out hardwired cross compiler name assumption that only m68k makes.
> > > 
> > > Signed-off-by: Rob Landley <rob@landley.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@linux-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

  reply	other threads:[~2007-10-11 12:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 22:22 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 [this message]
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
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=Pine.LNX.4.64.0710111443530.3729@anakin \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rob@landley.net \
    --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

all inboxes | Powered by JetHome®