All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: make install on ppc
Date: Tue, 28 Mar 2006 14:02:01 -0600	[thread overview]
Message-ID: <200603281402.02449.hollis@penguinppc.org> (raw)
In-Reply-To: <44298929.1060003@am.sony.com>

On Tuesday 28 March 2006 13:06, you wrote:
> Problem is for multi-platform binary builds, 'install' could mean differe=
nt
> things for the different platforms, so to support install, there needs
> to be some way to tell the build system what 'install' means that also
> works with the muti-platform makefile logic. =C2=A0The current powerpc ma=
kefiles
> don't have this, and it would take some non-trivial rework to add it.

That is for the distribution- or user-supplied installkernel script to deal=
=20
with.

> There is also the question of what install means when cross building.

So don't run make install when cross-compiling (unless of course your=20
installkernel script supports that).

I don't understand these objections. If someone's platform is so super-spec=
ial=20
that a script couldn't possibly know how to install a kernel, just don't ru=
n=20
make install!

=2DHollis

  reply	other threads:[~2006-03-28 20:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 14:08 [Fwd: Re: make install on ppc] Hans Fugal
2006-03-26 19:26 ` make install on ppc Hollis Blanchard
2006-03-26 20:43   ` Arnd Bergmann
2006-03-26 21:44   ` Hans Fugal
2006-03-27  1:42     ` Jin Qi Huang
2006-03-27  1:56       ` Brent Cook
2006-03-28  3:43         ` Hollis Blanchard
2006-03-28  3:59           ` Jin Qi Huang
2006-03-28 19:06           ` Geoff Levand
2006-03-28 20:02             ` Hollis Blanchard [this message]
2006-03-28 20:30               ` Geoff Levand
2006-03-28 21:13               ` Paul Mackerras

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=200603281402.02449.hollis@penguinppc.org \
    --to=hollis@penguinppc.org \
    --cc=geoffrey.levand@am.sony.com \
    --cc=linuxppc-dev@ozlabs.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.