From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root
Date: Sun, 18 Dec 2005 15:27:20 -0800 [thread overview]
Message-ID: <43A5F058.1060102@tlinx.org> (raw)
Unpacked 2.6.13.3 and made it read-only.
Using the "O=" param, built output tree for another machine as
a non-root user.
I wanted to create an installable kernel & module package to copy
to the new machine & install.
I noted new targets:
binrpm-pkg [& rpm-pkg], and
tarbz2-pkg [& targz-pkg, & tar-pkg].
Both seem to fail either for reasons that appear to be related to
not honoring the "O=" param, or attempting to actually install into
the root of my build-machine.
Should these targets work or have they not yet been converted to work
within the "O=" framework? In cases where the Makefile is attempting
to install into "<Root>/boot" or "<Root>/lib/modules" ,should I
expect the output to appear in "$O/boot" and "$O/lib/modules/"?
Please Cc responses to me, in addition to list, thanks.
-linda
next reply other threads:[~2005-12-18 23:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 23:27 Linda Walsh [this message]
2005-12-19 7:19 ` Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root Jan-Benedict Glaw
2005-12-19 22:12 ` Linda Walsh
2005-12-19 22:30 ` Jan-Benedict Glaw
2005-12-20 1:48 ` Linda Walsh
2005-12-30 6:33 ` patch for "scripts/package/buildtar" to pickup "localversion" on "/boot" file objects Linda A. Walsh
2005-12-30 10:15 ` Erik Mouw
2005-12-30 20:23 ` Linda A. Walsh
2005-12-20 15:41 ` Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root Nix
2005-12-20 15:58 ` Sam Ravnborg
2005-12-20 17:44 ` Nix
2005-12-20 17:37 ` Sam Ravnborg
2005-12-20 20:25 ` Al Viro
2005-12-21 7:49 ` Nix
2005-12-21 8:18 ` Al Viro
2005-12-21 11:22 ` Nix
2005-12-21 8:56 ` Sean
2005-12-21 8:56 ` Sean
2005-12-20 17:20 ` Ryan Anderson
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=43A5F058.1060102@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@vger.kernel.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.