public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linda Walsh <lkml@tlinx.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: make O="<dir>" install; output not relocated; 2.6.16.11(kbuild)
Date: Sat, 29 Apr 2006 09:08:06 +0200	[thread overview]
Message-ID: <20060429070806.GK25520@lug-owl.de> (raw)
In-Reply-To: <44524A3F.6060203@tlinx.org>

[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]

On Fri, 2006-04-28 10:00:47 -0700, Linda Walsh <lkml@tlinx.org> wrote:
> Jan-Benedict Glaw wrote:
> > The  modules_install  target uses O= for its _input_ files (that is,
> > for the readily compiled modules) and outputs to
> > $(INSTALL_MOD_PATH)/lib/modules/$VERSION/ .  So you may want to set
> > $(INSTALL_MOD_PATH) in the same way as you've set V= or O= before.
> >
> > If you're trying to prepare something to be copied over to a target
> > system, the tar-pkg, targz-pkg and tarbz2-pkg targets may be exactly
> > what you're searching for.
> >  
> Quite possibly. What about an installed kernel (apart from the
> modules)?  Will the kernel image and map, etc, get installed into
> the "INSTALL_MOD_PATH" as well?  It doesn't sound, intuitively,

`make modules_install' will never ever end up installing the kernel
image or the System.map or any other architecture-specific boot
images. It'll install the modules, nothing more.

The packaging scripts OTOH will of course also take that stuff.

> to be so from the environment variable name.
> > It's maybe a bit misleading, but `modules_install' isn't a compilation
> > run, it's an installation run. O= was ment to hold all
> > compiled/generated objects, but to have a working installation, you
> > need to break out of that (or have INSTALL_MOD_PATH set.)
>
>    Fair enough, but I'm more interested in where to specify
> the target location of the installed kernel and System.map as
> I don't always have modules for a generated kernel, but usually
> (near 100% :-)) have an installable kernel image.  For development,
> I could see it being useful to mount the target system's root in
> a local directory (like /mnt), then have the kernel build install
> to a target root of "/mnt".

Installing the kernel image is quite architecture specific; most
architectures use $(INSTALL_PATH), so this could be something like
/path/to/target_system/boot .  Though they may also re-run lilo or
something like that, so it's possibly not what you actually want to
use.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 für einen Freien Staat voll Freier Bürger"  | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-04-29  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28  6:34 make O="<dir>" install; output not relocated; 2.6.16.11(kbuild) Linda Walsh
2006-04-28  7:58 ` Jan-Benedict Glaw
2006-04-28 17:00   ` Linda Walsh
2006-04-29  7:08     ` Jan-Benedict Glaw [this message]
2006-04-29 14:30       ` Alistair John Strachan

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=20060429070806.GK25520@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.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