From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Gyu Sang Choi <gchoi-yyJJWgVhSYiVc3sceRu5cw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Error: can't read "CONFIG_SCSI": no such variable
Date: Thu, 20 Nov 2003 21:42:25 +0000 [thread overview]
Message-ID: <20031120214225.GO30485@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3FBD31F7.2070205-yyJJWgVhSYiVc3sceRu5cw@public.gmane.org>
On Thu, Nov 20, 2003 at 04:28:23PM -0500, Gyu Sang Choi wrote:
> I am trying to install ACPI2.0 into Linux-2.4.22 kernel.
> But I got a strange error message, when I try to store the configuration
> to file in "make xconfig".
> It is below
> ============================================
> Error: can't read "CONFIG_SCSI": no such variable
> ============================================
>
> If there is anyone to solve this problem already,
> please send me email.
Can you try splitting drivers/acpi/Config.in line 35 from:
else if [ "$CONFIG_SMP" = "y" ]; then
to:
else
if [ "$CONFIG_SMP" = "y" ]; then
This may solve your problem.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
prev parent reply other threads:[~2003-11-20 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 21:28 Error: can't read "CONFIG_SCSI": no such variable Gyu Sang Choi
[not found] ` <3FBD31F7.2070205-yyJJWgVhSYiVc3sceRu5cw@public.gmane.org>
2003-11-20 21:42 ` Matthew Wilcox [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=20031120214225.GO30485@parcelfarce.linux.theplanet.co.uk \
--to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=gchoi-yyJJWgVhSYiVc3sceRu5cw@public.gmane.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