From: Samuel Flory <sflory@rackable.com>
To: imunity@softhome.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Compiling using "make rpm" question PLEASE!!
Date: Sun, 06 Jul 2003 13:05:16 -0700 [thread overview]
Message-ID: <3F0880FC.1050101@rackable.com> (raw)
In-Reply-To: <courier.3F073637.000070EE@softhome.net>
imunity@softhome.net wrote:
>
> Still trying to figure out how to use "rpmbuild -bb"
What you need for that is a rpm spec file. Grab a kernel.src.rpm from
a distribution. Install it, and cd to /us/src/redhat (other distros may
have a different name in /usr./src). Now the sources, and patches
should be in SOURCE, and the spec file in SPEC. Now you can modify/add
the source/patches, and the spec. To create rpms you run "rpm -bb <spec
file>". Of course to get the i686 rpms you want you need to add
"--target i686".
Keep in mind this involves a lot of rpm spec file black magic. Also
most of time you will end up with at least 3 kernel rpms via this
method. You really don't want to do this unless you need to roll your
own custom releases of a distro for some reason.
prev parent reply other threads:[~2003-07-06 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 20:33 Kernel Compiling using "make rpm" question PLEASE!! imunity
2003-07-06 20:05 ` Samuel Flory [this message]
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=3F0880FC.1050101@rackable.com \
--to=sflory@rackable.com \
--cc=imunity@softhome.net \
--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