From: "B. Douglas Hilton" <bdhilton@charter.net>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: 2.4.21-pre6 - "mbool" causes xconfig failure
Date: Thu, 27 Mar 2003 18:29:26 -0500 [thread overview]
Message-ID: <3E838956.1000400@charter.net> (raw)
[1.] One line summary of the problem:
"make xconfig fails" drivers/net/Config.in: 188: unknown command
[2.] Full description of the problem/report:
Lines 188 and 189 of drivers/net/Config.in reference a define_mbool and dep_mbool
which causes xconfig to fail. Switching these to define_bool and dep_bool allows
it to work.
[3.] Keywords (i.e., modules, networking, kernel):
mbool Config.in CONFIG_EEPRO100_PIO
[4.] Kernel version (from /proc/version):
2.4.21-pre6
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
n/a
[6.] A small shell script or example program which triggers the
problem (if possible)
n/a
[7.] Environment
n/a
[7.1.] Software (add the output of the ver_linux script here)
n/a
[7.2.] Processor information (from /proc/cpuinfo):
n/a
[7.3.] Module information (from /proc/modules):
n/a
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
n/a
[7.5.] PCI information ('lspci -vvv' as root)
n/a
[7.6.] SCSI information (from /proc/scsi/scsi)
n/a
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
n/a
[X.] Other notes, patches, fixes, workarounds:
Just change "mbool" to "bool", not sure what the deal is here
or what an mbool is exactly.
reply other threads:[~2003-03-27 23:41 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=3E838956.1000400@charter.net \
--to=bdhilton@charter.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