From: Bill Davidsen <davidsen@tmr.com>
To: Thomas Davis <tadavis@lbl.gov>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix make rpm in 2.6 when using RH9 or Fedora..
Date: Sat, 14 Feb 2004 22:02:41 -0500 [thread overview]
Message-ID: <402EE151.4000807@tmr.com> (raw)
In-Reply-To: <402BD507.2040201@lbl.gov>
Thomas Davis wrote:
> Doing a 'make rpm' with any linux-2.6 (or probably, even linux-2.4
> kernel) will fail with the current RH/Fedora RPM macros.
>
> The failure message is this:
>
> Processing files: kernel-debuginfo-2.6.3rc1mm1-12
> error: Could not open %files file
> /usr/src/redhat/BUILD/kernel-2.6.3rc1mm1/debugfiles.list: No such file
> or directory
>
>
> RPM build errors:
> Could not open %files file
> /usr/src/redhat/BUILD/kernel-2.6.3rc1mm1/debugfiles.list: No such file
> or directory
> make: *** [rpm] Error 1
>
>
> The fix is this patch:
>
> --- linux-2.6/scripts/mkspec 2004-01-08 22:59:04.000000000 -0800
> +++ linux-2.6.3-rc1-mm1/scripts/mkspec 2004-02-12 00:02:55.000000000 -0800
> @@ -37,6 +37,7 @@
> echo "BuildRoot: /var/tmp/%{name}-%{PACKAGE_VERSION}-root"
> echo "Provides: $PROVIDES"
> echo "%define __spec_install_post /usr/lib/rpm/brp-compress || :"
> +echo "%define debug_package %{nil}"
> echo ""
> echo "%description"
> echo "The Linux Kernel, the operating system core itself"
Why do you want to disable the missing file check? As opposed to
providing the file?
I personally fix ther problem instead of disabling the check, the list
can be empty, of course.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2004-02-15 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 19:33 [PATCH] Fix make rpm in 2.6 when using RH9 or Fedora Thomas Davis
2004-02-15 3:02 ` Bill Davidsen [this message]
2004-02-16 0:03 ` Thomas Davis
2004-02-16 21:01 ` Sam Ravnborg
2004-02-17 4:14 ` Thomas Davis
2004-02-18 14:31 ` Bill Davidsen
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=402EE151.4000807@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tadavis@lbl.gov \
/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