From: "Randy.Dunlap" <rddunlap@osdl.org>
To: david nicol <whatever@davidnicol.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: configuration failure of 2.6.0-test11 on non-scsi system
Date: Wed, 3 Dec 2003 13:47:04 -0800 [thread overview]
Message-ID: <20031203134704.4a3b2abf.rddunlap@osdl.org> (raw)
In-Reply-To: <1070487104.30344.1.camel@plaza.davidnicol.com>
On 03 Dec 2003 15:31:45 -0600 david nicol <whatever@davidnicol.com> wrote:
| [david@plaza linux-2.6.0-test11]$ make menuconfig
| HOSTCC scripts/fixdep
| SHIPPED scripts/kconfig/zconf.tab.h
| HOSTCC scripts/kconfig/conf.o
| HOSTCC scripts/kconfig/mconf.o
| SHIPPED scripts/kconfig/zconf.tab.c
| SHIPPED scripts/kconfig/lex.zconf.c
| HOSTCC -fPIC scripts/kconfig/zconf.tab.o
| HOSTLLD -shared scripts/kconfig/libkconfig.so
| HOSTLD scripts/kconfig/mconf
| HOSTCC scripts/lxdialog/checklist.o
| HOSTCC scripts/lxdialog/inputbox.o
| HOSTCC scripts/lxdialog/lxdialog.o
| HOSTCC scripts/lxdialog/menubox.o
| HOSTCC scripts/lxdialog/msgbox.o
| HOSTCC scripts/lxdialog/textbox.o
| HOSTCC scripts/lxdialog/util.o
| HOSTCC scripts/lxdialog/yesno.o
| HOSTLD scripts/lxdialog/lxdialog
| scripts/kconfig/mconf arch/i386/Kconfig
| #
| # using defaults found in arch/i386/defconfig
| #
| arch/i386/defconfig:114: trying to assign nonexistent symbol ACPI_HT
| arch/i386/defconfig:176: trying to assign nonexistent symbol KCORE_ELF
| arch/i386/defconfig:177: trying to assign nonexistent symbol KCORE_AOUT
| arch/i386/defconfig:355: trying to assign nonexistent symbol
| SCSI_SYM53C8XX
Same for me down to here (without a .config file), but then menuconfig
runs for me.... I would guess either tools or libraries, but dunno.
| make[1]: *** [menuconfig] Segmentation fault
| make: *** [menuconfig] Error 2
| --
| Where the hell did I put my coffee?
Yes.
--
~Randy
MOTD: Always include version info.
prev parent reply other threads:[~2003-12-03 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 21:31 david nicol
2003-12-03 21:47 ` Randy.Dunlap [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=20031203134704.4a3b2abf.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=whatever@davidnicol.com \
/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®