All of lore.kernel.org
 help / color / mirror / Atom feed
From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Using RPMBUILD
Date: Thu, 28 Jul 2011 10:22:22 +0200	[thread overview]
Message-ID: <1311841343.3897.13.camel@thorin> (raw)
In-Reply-To: <4E303D6E.5020107@dra-hq.com>

Hi!

On Mit, 2011-07-27 at 12:31 -0400, Rodger Swann wrote:
[....]
> I have to use rpmbuild to build my kernel.   I also have to apply 
> patches and replace source code in the kernel source tree.   I have 
> figured out how to patch the files that I need patched by adding   Patch 
> blah and then AppyPatch in the spec file.  I then created a sym link to 
> the patch file in the rpmbuild SOURCES directory.
> 
> Now on to replacing the code in the source tree.  I have tried 
> untaring/unzipping the kernel source , putting in my source and 
> retarring and zipping, I have tried symlinking it, etc.  But each time 
> the build directory contains source code that is not the code that is 
> what I inserted and it is not clear to me where it is coming from.   I 

Apart from thing, that that is more of an rpmbuild than kernel problem:
The build directory (the one under */BUILD) is every time created from
scratch (unless some options are used).
In the .spec file, you have sources - usually a tar.gz - which gets
extracted by some command in the .spec file.
And than, the patches are applied as listed with the %patch line.

You should actually see in the shell, what the .spec file is actually
doing.

> am fairly frustrated so if anyway has encountered this or knows how to 
> do it I would appreciate the help.    Spoon feeding is not required a I 
> will gladly rtfm but I will need a nudge in the right direction.

	Bernd
-- 
Bernd Petrovitsch                  Email : bernd at petrovitsch.priv.at
                     LUGA : http://www.luga.at

      reply	other threads:[~2011-07-28  8:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 16:31 Using RPMBUILD Rodger Swann
2011-07-28  8:22 ` Bernd Petrovitsch [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=1311841343.3897.13.camel@thorin \
    --to=bernd@petrovitsch.priv.at \
    --cc=kernelnewbies@lists.kernelnewbies.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.