mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 64-bit sources
Date: Fri, 29 Feb 2008 11:36:43 -0500	[thread overview]
Message-ID: <28962.1204303003@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 29 Feb 2008 11:25:58 EST." <Pine.LNX.4.61.0802291123280.23162@chaos.analogic.com>

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

On Fri, 29 Feb 2008 11:25:58 EST, "linux-os (Dick Johnson)" said:
> 
> Yes. The RPM contains only patches and the patches won't
> patch a 2.6.11 kernel either! Perhaps they need to be
> in some undefined order.

Umm... I just checked that specific RPM, and that RPM *does* contain all that
you need. In particular, the following *are* in there:

kernel-2.6.spec
linux-2.6.11.tar.bz2
patch-2.6.12-rc5-neutered.bz2  <- probably why they won't patch a 2.6.11

The spec file lists all the *.patch files and the order to apply them in.  It
even has a whole bunch of *.config files.

Your best best is to 'rpm -ivh' that RPM - that will put the pieces in
/usr/src/redhat/SOURCES and /usr/src/redhat/SPECS.  'rpmbuild kernel.spec'
(with appropriate flags, you probably want '--target x86_64' if you want
a  64-bit build only).  Adding patches is a matter of dropping the patch in
/usr/src/redhat/SOURCES and adding a few lines to the kernel-2.6.spec file.



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

  reply	other threads:[~2008-02-29 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 15:07 linux-os (Dick Johnson)
2008-02-29 15:31 ` Jan Engelhardt
2008-02-29 16:25   ` linux-os (Dick Johnson)
2008-02-29 16:36     ` Valdis.Kletnieks [this message]
2008-02-29 18:24       ` linux-os (Dick Johnson)

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=28962.1204303003@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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

all inboxes | Powered by JetHome®