From: Pavel Machek <pavel@ucw.cz>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig CROSS_COMPILE option
Date: Wed, 9 Sep 2009 10:08:33 +0200 [thread overview]
Message-ID: <20090909080833.GA28586@elf.ucw.cz> (raw)
In-Reply-To: <20090907183801.379228BF3F@magilla.sf.frob.com>
On Mon 2009-09-07 11:38:01, Roland McGrath wrote:
> > Yes that would be very nice. Editing Makefile every time I
> > crosscomppile for arm sucks.
>
> The other trick I can recommend is to write a GNUmakefile containing:
>
> ARCH=foo
> CROSS_COMPILE=foo-linux-
> include Makefile
Hehe, thanks.
> (GNU make reads GNUmakefile in preference to Makefile.)
> But this manual hackery is still not nearly as nice as the automagic way.
>
> > But... do we need an option for subarch, too? And will Kconfig system
> > handle that?
>
> I'm not sure I follow exactly what your concern is. I am mostly familiar
> with doing x86 and powerpc builds. For both of those, the kernel config
> sets whether it's the 32-bit or 64-bit world.
Well, my concern is that your patch allows me to set $CROSS_COMPILE,
but I need to set $ARCH too, to get useful result. So I can't actually
see how to use your patch.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-09 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 0:29 [PATCH] kconfig CROSS_COMPILE option Roland McGrath
2009-09-07 13:09 ` Pavel Machek
2009-09-07 18:38 ` Roland McGrath
2009-09-09 8:08 ` Pavel Machek [this message]
2009-09-09 13:20 ` Geert Uytterhoeven
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=20090909080833.GA28586@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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