From: Martin List-Petersen <martin@list-petersen.dk>
To: Jay Denebeim <denebeim@deepthot.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Could not open debufiles.list on Redhat 9 kernel compile
Date: 13 Jul 2003 19:00:34 +0200 [thread overview]
Message-ID: <1058115633.15138.17.camel@loke> (raw)
In-Reply-To: <slrnbh2vlf.ia6.denebeim@hotblack.deepthot.org>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Yep .. all -b switches have been moved from rpm to rpmbuild.
So if you edit the Makefile, replacing call of "rpm" with "rpmbuild" it
works.
Regards,
Martin List-Petersen
martin at list-petersen dot dk
--
Twas FORTRAN as the doloop goes
Did logzerneg the ifthen block
All kludgy were the function flows
And subroutines adhoc.
Beware the runtime-bug my friend
squrooneg, the false goto
Beware the infiniteloop
And shun the inprectoo.
-- "OUTCONERR," to the scheme of "Jabberwocky"
On Sun, 2003-07-13 at 17:45, Jay Denebeim wrote:
> I've seen quite a few references to this with google, I haven't seen a
> solution. The problem is making a stock kernel with 'make rpm' on a
> redhat 9 system. Redhat has done something to rpm with version 9 that
> is causing it to create a debug package for every package you make.
> Unfortunately whatever it's doing is busted for stock kernels.
>
> I've been unable to find a way to turn off this generation. There is
> a variable %_enable_debug_packages 1 in the redhat macros, I've turned
> it off, but that hasn't helped.
>
> So, how do I disable this 'feature'? Does anyone know?
>
> Jay
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-13 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 15:45 Could not open debufiles.list on Redhat 9 kernel compile Jay Denebeim
2003-07-13 17:00 ` Martin List-Petersen [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=1058115633.15138.17.camel@loke \
--to=martin@list-petersen.dk \
--cc=denebeim@deepthot.org \
--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 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.