From: Peter Jay Salzman <p@dirac.org>
To: linux-kernel@vger.kernel.org
Subject: something's wrong with the 2.4.12 compilation
Date: Sun, 14 Oct 2001 23:50:17 -0700 [thread overview]
Message-ID: <20011014235017.A17420@dirac.org> (raw)
hi all,
grabbed 2.4.12, copied .config from my current 2.4.10, did a make oldconfig
and make dep && make bzImage. here's the error:
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[3]: *** [ieee1284_ops.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.12/drivers/parport'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.12/drivers/parport'
make[1]: *** [_subdir_parport] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.12/drivers'
make: *** [_dir_drivers] Error 2
satan#
i don't need 2.4.12 for anything in particular, so please don't feel like i
need help or anything. i'm perfectly happy with 2.4.10.
my only concern is for the kernel itself. someone out there may really
depend on the new release.
if you want to ask any questions or a copy of .config, please email me at
p(at)dirac.org.
thank you! :)
pete
--
"You may not use the Software in connection with any site that disparages
Microsoft, MSN, MSNBC, Expedia, or their products or services ..."
-- Clause from license for FrontPage 2002
next reply other threads:[~2001-10-15 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 6:50 Peter Jay Salzman [this message]
2001-10-15 9:35 ` something's wrong with the 2.4.12 compilation Robert Szentmihalyi
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=20011014235017.A17420@dirac.org \
--to=p@dirac.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.