From: Duncan Sands <baldrick@wanadoo.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 BK compile failure in dmi_scan: `BROKEN_PNP_BIOS' undeclared
Date: Sat, 5 Jul 2003 22:02:40 +0200 [thread overview]
Message-ID: <200307052202.40781.baldrick@wanadoo.fr> (raw)
In-Reply-To: <1057412245.23488.5.camel@dhcp22.swansea.linux.org.uk>
On Saturday 05 July 2003 15:37, Alan Cox wrote:
> On Sad, 2003-07-05 at 12:56, Duncan Sands wrote:
> > make[2]: Entering directory `/home/duncan/linux-2.4/arch/i386/kernel'
> > gcc -D__KERNEL__ -I/home/duncan/linux-2.4/include -Wall
> > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
> > -nostdinc -iwithprefix include -DKBUILD_BASENAME=dmi_scan -c -o
> > dmi_scan.o dmi_scan.c
> > dmi_scan.c: In function `exploding_pnp_bios':
> > dmi_scan.c:521: error: `BROKEN_PNP_BIOS' undeclared (first use in this
> > function) dmi_scan.c:521: error: (Each undeclared identifier is reported
> > only once dmi_scan.c:521: error: for each function it appears in.)
> > dmi_scan.c: In function `dmi_decode':
> > dmi_scan.c:944: warning: unused variable `data'
>
> Marcelo hasn't yet applied all the changes I sent him, including some
> that depend on each other. Just pull that change from -ac or wait
I didn't need to wait long - thanks!
D.
prev parent reply other threads:[~2003-07-05 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 11:56 2.4 BK compile failure in dmi_scan: `BROKEN_PNP_BIOS' undeclared Duncan Sands
2003-07-05 13:37 ` Alan Cox
2003-07-05 20:02 ` Duncan Sands [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=200307052202.40781.baldrick@wanadoo.fr \
--to=baldrick@wanadoo.fr \
--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;
as well as URLs for NNTP newsgroup(s).