From: Kelly French <kfrench@pebbles.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: make rpm is not documented
Date: Sat, 23 Mar 2002 13:19:39 -0500 [thread overview]
Message-ID: <20020323131939.A9293@pebbles.net> (raw)
In-Reply-To: <20020320154100.D21789@pcmaftoul.esrf.fr> <E16nhv9-0002XX-00@the-village.bc.nu>
On Wed, Mar 20, 2002 at 03:22:35PM +0000, Alan Cox wrote:
> > Second stuff, make rpm don't work for me on suse's kernel.
>
> Ask SuSE 8)
>
> > Didn't yet watched what is the problem, but seems to be related with
> > EXTRAVERSION or something like this.
>
> At least some versions of the script didnt like multiple '-' symbols.
> Gerald Britton fixed this for 2.4.18
>
> > I will have further look and will try to say as much as I can with my
> > poor knowledge.
>
> Basically the thing works with
>
> make config/menuconfig/xconfig
> if you use make menu/xconfig then run make oldconfig (I dont trust xconfig..)
> make rpm
>
> [wait.. wait.. wait.. ]
>
> rpm --install
>
> add to lilo.conf
>
> enjoy
Any chance we can copy the .config to /boot/config-$version?
--- scripts/mkspec.orig Sat Mar 23 13:13:19 2002
+++ scripts/mkspec Sat Mar 23 13:13:37 2002
@@ -35,6 +35,7 @@
echo 'INSTALL_MOD_PATH=$RPM_BUILD_ROOT make modules_install'
echo 'cp arch/i386/boot/bzImage $RPM_BUILD_ROOT'"/boot/vmlinuz-$VERSION.$PATCHLEVEL.$SUBLEVEL$EXTRAVERSION"
echo 'cp System.map $RPM_BUILD_ROOT'"/boot/System.map-$VERSION.$PATCHLEVEL.$SUBLEVEL$EXTRAVERSION"
+echo 'cp .config $RPM_BUILD_ROOT'"/boot/config-$VERSION.$PATCHLEVEL.$SUBLEVEL$EXTRAVERSION"
echo ""
echo "%clean"
echo '#echo -rf $RPM_BUILD_ROOT'
-kf
next prev parent reply other threads:[~2002-03-23 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 14:41 Samuel Maftoul
2002-03-20 15:22 ` Alan Cox
2002-03-20 15:30 ` Samuel Maftoul
2002-03-23 18:19 ` Kelly French [this message]
2002-03-23 19:06 ` 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=20020323131939.A9293@pebbles.net \
--to=kfrench@pebbles.net \
--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
all inboxes | Powered by JetHome®