From: Bruce Harada <bruce@ask.ne.jp>
To: David Ronis <ronis@montroll.chem.mcgill.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Module Build Failure in 2.4.12
Date: Sun, 14 Oct 2001 12:50:43 +0900 [thread overview]
Message-ID: <20011014125043.4031e6d8.bruce@ask.ne.jp> (raw)
In-Reply-To: <200110140325.f9E3Pttt002153@montroll.chem.mcgill.ca>
In-Reply-To: <200110140325.f9E3Pttt002153@montroll.chem.mcgill.ca>
On Sat, 13 Oct 2001 23:25:55 -0400
David Ronis <ronis@montroll.chem.mcgill.ca> wrote:
> I've been trying to build 2.4.12 on an i586-linux-gnu box [an out of the
> package Slackware8.0 system]. The build fails in building the parport
> driver
> module. Specfically:
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.12/include -Wall -Wstrict-prototypes
> -Wno-
> trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe
> -mpref
> erred-stack-boundary=2 -march=i586 -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
> func
> tion)
> 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
> func
> tion)
> make[2]: *** [ieee1284_ops.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.4.12/drivers/parport'
> make[1]: *** [_modsubdir_parport] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.12/drivers'
> make: *** [_mod_drivers] Error 2
[SNIP]
> I'm going to remove this support and try again, but the problem should be
> fixed.
It has been, many times in the last few days... try searching the l-k archives
before posting.
Bruce
prev parent reply other threads:[~2001-10-14 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 3:25 David Ronis
2001-10-14 3:50 ` Bruce Harada [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=20011014125043.4031e6d8.bruce@ask.ne.jp \
--to=bruce@ask.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=ronis@montroll.chem.mcgill.ca \
/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®