From: Ben Pfaff <pfaffben@msu.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make rpm
Date: 28 Jul 2001 21:05:46 -0400 [thread overview]
Message-ID: <87g0bg7ded.fsf@pfaffben.user.msu.edu> (raw)
In-Reply-To: <E15QeJf-0008O8-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Sun, 29 Jul 2001 01:20:19 +0100 (BST)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> I've been meaning to do this one for a while and I now have it working so
> that with my current -ac kernel working tree I can type
>
> make rpm
>
> and out puts kernel-2.4.7ac3-1.i386.rpm
>
> All this took was the pieces below.
>
> Anyone care to knock up a "make dpkg" to go with it ?
Debian has had a package that does this for years now. It's
called `kernel-package' and works through a program called
`make-kpkg' that does all sorts of nice things. Using
kernel-package, you could implement `make dpkg' as a single
command: `make-kpkg kernel_image'.
Here's some more about kernel-package in the program's own words:
blp:~(0)$ make-kpkg --targets
Known Targets are:
===============================================================================
| Targets | Automatically builds |
===============================================================================
| clean | |
| buildpackage | Builds the whole package |
| binary | Builds kernel_{source,headers,image,doc} |
| binary-indep | |
| kernel_source | |
| kernel_doc | |
| binary-arch | |
| kernel_headers | |
| kernel_image | Builds build |
| build | |
| modules | |
| modules_image | |
| modules_config | |
| modules_clean | |
| configure | If you wish to edit files |
| debian | generated by make config |
| debian | Creates ./debian dir, and |
| | optionally patches the source |
===============================================================================
See /usr/share/kernel-package/rules for details.
blp:~(0)$ make-kpkg --help
This program should be run in a linux kernel source top level directory.
/usr/share/doc/kernel-package/Problems.gz contains a list of known problems.
usage: make-kpkg [options] target [target ...]
where options are:
--help This message.
--revision number The debian revision number. ([a-zA-Z.+0-9]) (Must
have digit, no hyphen allowed)
--flavour foo an additional kernel sub-version. ([-a-z.+0-9])
OBSOLETE
--append-to-version foo
--append_to_version foo an additional kernel sub-version. ([-a-z.+0-9])
Does not require editing the kernel Makefile
over rides env var APPEND_TO_VERSION.
requires a make-kpg clean
--added-modules foo
--added_modules foo Comma/space separated list of add on modules
affected by the modules_<blah> targets
--added-patches bar
--added_patches bar Comma/space separated list of patches applicable
when patch_the_kernel is turned on
--arch foo architecture
--cross-compile
--cross_compile target string
--subarch bar Set the subarch for the image being compiled
(have to be on a compatible machine).
--arch-in-name
--arch_in_name Embed the subarch in the image package name
--initrd Create a image package suitable for initrd
--pgpsign name An ID used to sign the changes file using pgp.
--targets Lists the known targets.
--zimage Create a kernel using zImage rather than bzImage
--bzimage Create a kernel using bzImage (in case the site
wide default is zimage, as set in
/etc/kernel-pkg.conf)
--rootcmd method A command that provides a means of gaining
superuser access (for example, `sudo' or
`fakeroot') as needed by dpkg-buildpackages'
-r option. This is only relevant for the
buildpackage target.
--us This option is passed to dpkg-buildpackage, and
directs that package not to sign the
source. This is only relevant for the
buildpackage target.
--uc This option is passed to dpkg-buildpackage, and
directs that package not to sign the
changelog. This is only relevant for the
buildpackage target.
Use one of --zimage or --bzimage, or none, but not both.
Option Format: The options may be shortened to the smallest unique
string, and may be entered with either a - or a -- prefix, and you may
use a space between an option string and a value. Please refer to man
Getopt::Long for details on how the options may be entered.
Version: $Revision: 1.60 $
Manoj Srivastava <srivasta@debian.org>
blp:~(0)$
next prev parent reply other threads:[~2001-07-29 1:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-29 0:20 make rpm Alan Cox
2001-07-29 0:33 ` Horst von Brand
2001-07-29 1:05 ` Ben Pfaff [this message]
2001-07-29 2:53 ` Mike Touloumtzis
2001-07-29 8:22 ` Kai Henningsen
2001-07-29 11:58 ` Jean Charles Delepine
2001-07-29 12:19 ` Wichert Akkerman
2001-07-29 14:49 ` Steve Kowalik
2001-07-29 15:26 ` Wichert Akkerman
2001-07-29 21:23 ` Dominik Kubla
2001-07-30 19:34 ` Andreas Dilger
[not found] <no.id>
2001-07-29 0:38 ` Alan Cox
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=87g0bg7ded.fsf@pfaffben.user.msu.edu \
--to=pfaffben@msu.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox