From: Matthew Wilcox <willy@debian.org>
To: Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: 2.5.44: How to decode call trace
Date: Wed, 23 Oct 2002 12:48:46 +0100 [thread overview]
Message-ID: <20021023124846.L27461@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <878z0p1m2y.fsf@goat.bogus.local>; from olaf.dietsche#list.linux-kernel@t-online.de on Wed, Oct 23, 2002 at 12:33:25PM +0200
On Wed, Oct 23, 2002 at 12:33:25PM +0200, Olaf Dietsche wrote:
> When I build with "make -k EXTRA_CFLAGS=-g EXTRA_LDFLAGS=-g bzImage",
> I get a ton of error messages from drivers/acpi/include/actypes.h and
> other acpi related stuff, starting with: #error ACPI_MACHINE_WIDTH not
> defined. Maybe this is not the usual way to build with -g, but I don't
> get these errors with "make -k bzImage". Maybe someone is interested
> in this.
Not really. Users shouldn't be overriding EXTRA_CFLAGS, it's for the
benefit of various parts of the kernel. Some other parts of the kernel
you break by doing this:
./arch/i386/mach-generic/Makefile:EXTRA_CFLAGS += -I../kernel
./drivers/ide/pci/Makefile:EXTRA_CFLAGS := -Idrivers/ide
./drivers/message/fusion/Makefile:EXTRA_CFLAGS += ${MPT_CFLAGS}
./drivers/usb/storage/Makefile:EXTRA_CFLAGS := -Idrivers/scsi
./fs/smbfs/Makefile:EXTRA_CFLAGS += -DSMBFS_PARANOIA
./fs/xfs/Makefile:EXTRA_CFLAGS += -Ifs/xfs -funsigned-char
./sound/oss/emu10k1/Makefile: EXTRA_CFLAGS += -DEMU10K1_DEBUG
The normal way to do what you want is to edit the Makefile and add -g
directly to CFLAGS.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-10-23 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87elai82xb.fsf@goat.bogus.local.suse.lists.linux.kernel>
2002-10-23 3:50 ` Andi Kleen
2002-10-23 9:37 ` bert hubert
2002-10-23 12:30 ` Olaf Dietsche
2002-10-23 10:33 ` Olaf Dietsche
2002-10-23 11:48 ` Matthew Wilcox [this message]
2002-10-23 12:26 ` Olaf Dietsche
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=20021023124846.L27461@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf.dietsche#list.linux-kernel@t-online.de \
/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
Powered by JetHome