From: "Fabio" <fabio.adamo@inwind.it>
To: <linux-kernel@vger.kernel.org>
Subject: BUG - Kernel 2.4.12 doesn't compile
Date: Fri, 12 Oct 2001 21:44:26 +0200 [thread overview]
Message-ID: <000d01c15356$6c2bfec0$0100a8c0@leopoldo> (raw)
I use a RH 7.1 ad trying to compile the kernel v. 2.4.12 i get the error you
can see here:
-----------------------------------------------------
fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -DMODULE -c -o
share.o share.c
gcc -D__KERNEL__ -I/usr/local/src/linux-2.4.12/include -Wall -Wstrict-protot
ypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -DMODULE -c -o
ieee1284.o ieee1284.c
gcc -D__KERNEL__ -I/usr/local/src/linux-2.4.12/include -Wall -Wstrict-protot
ypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -DMODULE -c -o
ieee1284_ops.o ieee1284_ops.c
ieee1284_ops.c: In function `ecp_forward_to_reverse':
ieee1284_ops.c:365: `IEEE1284_PH_DIR_UNKNOWN' undeclared (first use in this
function)
ieee1284_ops.c:365: (Each undeclared identifier is reported only once
ieee1284_ops.c:365: for each function it appears in.)
ieee1284_ops.c: In function `ecp_reverse_to_forward':
ieee1284_ops.c:397: `IEEE1284_PH_DIR_UNKNOWN' undeclared (first use in this
function)
make[2]: *** [ieee1284_ops.o] Error 1
make[2]: Leaving directory `/usr/local/src/linux-2.4.12/drivers/parport'
make[1]: *** [_modsubdir_parport] Error 2
make[1]: Leaving directory `/usr/local/src/linux-2.4.12/drivers'
make: *** [_mod_drivers] Error 2
----------------------------------------------------
Thank you & goodbye.
Fabio Adamo
next reply other threads:[~2001-10-12 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 19:44 Fabio [this message]
2001-10-12 21:27 ` Lukasz Trabinski
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='000d01c15356$6c2bfec0$0100a8c0@leopoldo' \
--to=fabio.adamo@inwind.it \
--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®