From: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
To: acurtis@onz.com
Cc: Dan Malek <dan@embeddededge.com>, linuxppc-dev@lists.linuxppc.org
Subject: RE: Cross compile helper patch
Date: 28 Aug 2002 14:01:09 +0200 [thread overview]
Message-ID: <1030536069.28699.14.camel@spawn> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFOEEKDLAA.acurtis@onz.com>
On Wed, 2002-08-28 at 06:22, Allen Curtis wrote:
>
> > It only goes in your local version of this file. Everyone has a different
> > way they want their cross compilation to work, and those of us that use
> > native systems don't like this in the Makefile. This is the historically
> > consistent response to everyone that has submitted a similar
> > patch over the years.
>
> A two line change to a make file is not exactly cluttering anything up. If
> you are doing native development then you use the distribution as it is
> provided. Only if you are doing cross development do you need to create
> these files. Just a nice logical in the developers face solution to a
> problem that has been solved a 1000 time before.
>
This is what I do when cross compiling
make ARCH=ppc CROSS_COMPILE=powerpc-linux-
Needs no changes to the makefile.
--
Kenneth Johansson
Ericsson AB Tel: +46 8 404 71 83
Borgafjordsgatan 9 Fax: +46 8 404 72 72
164 80 Stockholm kenneth.johansson@etx.ericsson.se
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-28 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 0:02 Cross compile helper patch Allen Curtis
2002-08-28 4:05 ` Dan Malek
2002-08-28 4:22 ` Allen Curtis
2002-08-28 5:12 ` Dan Malek
2002-08-28 12:01 ` Kenneth Johansson [this message]
2002-08-28 14:33 ` Allen Curtis
2002-08-28 15:08 ` Jerry Van Baren
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=1030536069.28699.14.camel@spawn \
--to=kenneth.johansson@etx.ericsson.se \
--cc=acurtis@onz.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.