From: Yaroslav Klyukin <yklyukin@demandware.com>
To: linux-config@vger.kernel.org
Subject: kernel rpm with no module support.
Date: Mon, 27 Feb 2006 14:14:05 -0500 [thread overview]
Message-ID: <44034F7D.4030200@demandware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
Patch that allows to build monolithic kernel (CONFIG_MODULES disabled) RPMs.
Not sure where to send it. If this is the wrong place, please forward it
appropriately.
[-- Attachment #2: nomodules.patch --]
[-- Type: text/plain, Size: 1216 bytes --]
--- scripts/package/mkspec.orig 2006-02-27 18:54:22.000000000 +0000
+++ scripts/package/mkspec 2006-02-27 19:02:03.000000000 +0000
@@ -17,10 +17,16 @@
fi
# starting to output the spec
-if [ "`grep CONFIG_DRM=y .config | cut -f2 -d\=`" = "y" ]; then
+if [ "`grep CONFIG_DRM=y .config | cut -f2 -d\=`" == "y" ]; then
PROVIDES=kernel-drm
fi
+if [ "`grep CONFIG_MODULES=y .config`" == "" ]; then
+ MODULES=false
+else
+ MODULES=true
+fi
+
PROVIDES="$PROVIDES kernel-$KERNELRELEASE"
__KERNELRELEASE=`echo $KERNELRELEASE | sed -e "s/-//g"`
@@ -64,7 +70,9 @@
echo "%install"
echo 'mkdir -p $RPM_BUILD_ROOT/boot $RPM_BUILD_ROOT/lib $RPM_BUILD_ROOT/lib/modules'
-echo 'INSTALL_MOD_PATH=$RPM_BUILD_ROOT make %{_smp_mflags} modules_install'
+if $MODULES ; then
+ echo 'INSTALL_MOD_PATH=$RPM_BUILD_ROOT make %{_smp_mflags} modules_install'
+fi
echo 'cp $KBUILD_IMAGE $RPM_BUILD_ROOT'"/boot/vmlinuz-$KERNELRELEASE"
echo 'cp System.map $RPM_BUILD_ROOT'"/boot/System.map-$KERNELRELEASE"
@@ -77,6 +85,8 @@
echo "%files"
echo '%defattr (-, root, root)'
echo "%dir /lib/modules"
-echo "/lib/modules/$KERNELRELEASE"
+if $MODULES ; then
+ echo "/lib/modules/$KERNELRELEASE"
+fi
echo "/boot/*"
echo ""
reply other threads:[~2006-02-27 19:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44034F7D.4030200@demandware.com \
--to=yklyukin@demandware.com \
--cc=linux-config@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).