From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 391] New: 2.5.62-bk5 compile failure with gcc-2.95
Date: Sat, 22 Feb 2003 13:03:07 -0800 [thread overview]
Message-ID: <2330000.1045947787@[10.10.2.4]> (raw)
http://bugme.osdl.org/show_bug.cgi?id=391
Summary: 2.5.62-bk5 compile failure with gcc-2.95
Kernel Version: 2.5.62-bk5
Status: NEW
Severity: blocking
Owner: ambx1@neo.rr.com
Submitter: plars@austin.ibm.com
Distribution:Debian stable
Hardware Environment:pIII-800
Software Environment:gcc-2.95
Problem Description:
I got this compile failure on the nightly bk pull test last night. It should
match up to what's in -bk5:
gcc -Wp,-MD,drivers/pnp/.interface.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=i686 -Iinclude/asm-i386/mach-default
-nostdinc -iwithprefix include -DKBUILD_BASENAME=interface
-DKBUILD_MODNAME=interface -c -o drivers/pnp/interface.o drivers/pnp/interface.c
drivers/pnp/interface.c: In function `pnp_set_current_resources':
drivers/pnp/interface.c:438: parse error before `struct'
drivers/pnp/interface.c:440: `res' undeclared (first use in this function)
drivers/pnp/interface.c:440: (Each undeclared identifier is reported only once
drivers/pnp/interface.c:440: for each function it appears in.)
drivers/pnp/interface.c:448: `nport' undeclared (first use in this function)
drivers/pnp/interface.c:468: `nmem' undeclared (first use in this function)
drivers/pnp/interface.c:488: `nirq' undeclared (first use in this function)
drivers/pnp/interface.c:500: `ndma' undeclared (first use in this function)
make[2]: *** [drivers/pnp/interface.o] Error 1
make[1]: *** [drivers/pnp] Error 2
make: *** [drivers] Error 2
Steps to reproduce:
I tried reproducing this with gcc-3.2 and it compiles fine, but when I switch to
2.95 it breaks.
reply other threads:[~2003-02-22 20:53 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='2330000.1045947787@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--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
all inboxes | Powered by JetHome®