From: Sam Ravnborg <sam@ravnborg.org>
To: Josh Hunt <josh@scalex86.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
kiran@scalex86.org, mingo@elte.hu
Subject: Re: [PATCH] Add vmlinux to kernel rpm - updated description
Date: Sun, 15 Feb 2009 09:01:36 +0100 [thread overview]
Message-ID: <20090215080136.GA26481@uranus.ravnborg.org> (raw)
In-Reply-To: <20090212051057.GC12732@localhost.localdomain>
On Wed, Feb 11, 2009 at 09:10:57PM -0800, Josh Hunt wrote:
> Resending with updated description:
>
> We are building an automated system to test kernels weekly and need to
> provide an rpm to our QA dept. We would like to use the ability to create
> kernel rpms already in the kernel's Makefile, but need the vmlinux file
> included in the rpm for later debugging. This patch adds a compressed vmlinux to
> the kernel rpm when doing a make rpm-pkg or binrpm-pkg and upon install
> places the vmlinux file in /boot.
>
> Signed-off-by: Josh Hunt <josh@scalex86.org>
Applied, but...
>
> Index: linux-2.6.28/scripts/package/mkspec
> ===================================================================
> --- linux-2.6.28.orig/scripts/package/mkspec 2008-12-24
> 15:26:37.000000000 -0800
> +++ linux-2.6.28/scripts/package/mkspec 2009-01-21
> 16:53:03.000000000 -0800
> @@ -86,6 +86,14 @@ echo "%endif"
> echo 'cp System.map $RPM_BUILD_ROOT'"/boot/System.map-$KERNELRELEASE"
>
> echo 'cp .config $RPM_BUILD_ROOT'"/boot/config-$KERNELRELEASE"
> +
> +echo "%ifnarch ppc64"
> +echo 'cp vmlinux vmlinux.orig'
why is this relevant for all architectures except ppc64?
This is not addressed neither in a comment nor in the changelog.
Sam
next prev parent reply other threads:[~2009-02-15 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 5:10 [PATCH] Add vmlinux to kernel rpm - updated description Josh Hunt
2009-02-15 8:01 ` Sam Ravnborg [this message]
2009-02-18 8:05 ` Josh Hunt
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=20090215080136.GA26481@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=josh@scalex86.org \
--cc=kiran@scalex86.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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