From: Stephane Wirtel <stephane.wirtel@belgacom.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux 2.5.31 - compile error with pnpbios in pnpbios_core.c
Date: Sun, 11 Aug 2002 11:04:27 +0200 [thread overview]
Message-ID: <20020811090427.GA7494@stargate.lan> (raw)
there are the lines of this error
make[3]: Entering directory `/usr/src/linux-2.5.31/drivers/pnp'
gcc -Wp,-MD,./.pnpbios_core.o.d -D__KERNEL__
-I/usr/src/linux-2.5.31/include -Wall -Wstrict-prototypes -Wno-trigraphs
-O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -nostdinc
-iwithprefix include -DKBUILD_BASENAME=pnpbios_core -DEXPORT_SYMTAB
-c -o pnpbios_core.o pnpbios_core.c
pnpbios_core.c: In function `call_pnp_bios':
pnpbios_core.c:166: invalid lvalue in unary `&'
pnpbios_core.c:166: invalid lvalue in unary `&'
pnpbios_core.c:168: invalid lvalue in unary `&'
pnpbios_core.c:168: invalid lvalue in unary `&'
pnpbios_core.c: In function `pnpbios_init':
pnpbios_core.c:1275: invalid lvalue in unary `&'
pnpbios_core.c:1275: invalid lvalue in unary `&'
pnpbios_core.c:1276: invalid lvalue in unary `&'
pnpbios_core.c:1276: invalid lvalue in unary `&'
pnpbios_core.c:1277: invalid lvalue in unary `&'
pnpbios_core.c:1277: invalid lvalue in unary `&'
make[3]: *** [pnpbios_core.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.5.31/drivers/pnp'
make[2]: *** [pnp] Error 2
make[2]: Leaving directory `/usr/src/linux-2.5.31/drivers'
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.31'
make: *** [bzImage] Error 2
bash-2.05a#
best regards,
stephane wirtel
--
Stephane Wirtel <stephane.wirtel@belgacom.net>
Web : www.linux-mons.be "Linux Is Not UniX !!!"
Address :
Rue de cartier, 53
6030 Marchienne-au-Pont
Belgium
Phone : +32 474 768 072
reply other threads:[~2002-08-11 9:00 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=20020811090427.GA7494@stargate.lan \
--to=stephane.wirtel@belgacom.net \
--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®