public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <eric.piel@tremplin-utc.net>
To: Tobias Oed <tobias.oed@octant-fr.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	matthew@wil.cx, Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: 2.6.25-rc6 compile error in drivers/acpi/osl.c
Date: Sat, 22 Mar 2008 15:32:04 +0100	[thread overview]
Message-ID: <47E51864.5000107@tremplin-utc.net> (raw)
In-Reply-To: <47E508B3.8070801@octant-fr.com>

(added Randy as CC just in case it ends up being a problem with 
7ce9573e093891f5807e6e50f3bd2012f1e5d0fe)
Tobias Oed wrote:
> Hello,
> compiling 2.6.25-rc6 on my up to date fedora 8 system ends with
> 
>   CC      drivers/acpi/osl.o
> drivers/acpi/osl.c:60:38: error: n: No such file or directory
> drivers/acpi/osl.c: In function ‘acpi_os_table_override’:
> drivers/acpi/osl.c:334: error: ‘AmlCode’ undeclared (first use in this 
> function)
> drivers/acpi/osl.c:334: error: (Each undeclared identifier is reported 
> only once
> drivers/acpi/osl.c:334: error: for each function it appears in.)
> make[2]: *** [drivers/acpi/osl.o] Error 1
> make[1]: *** [drivers/acpi] Error 2
> make: *** [drivers] Error 2
> 
> Config attached
Hi Tobias,
First, you haven't sent the correct .config file (this one is dated "Fri 
Mar 14 21:06:35 2008").

To fix your problem you just need to "make menuconfig" and change 
ACPI_CUSTOM_DSDT_FILE from "n" to "".

Now the question is: how did you end up with this error? Is it just you 
who mistook while answering the questions of "make oldconfig" or did 
this "n" appeared automatically because was not ACPI_CUSTOM_DSDT is set. 
In which case this is a bug in the kernel.

Eric

  reply	other threads:[~2008-03-22 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22 13:25 2.6.25-rc6 compile error in drivers/acpi/osl.c Tobias Oed
2008-03-22 14:32 ` Eric Piel [this message]
2008-03-22 15:04   ` Tobias Oed

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=47E51864.5000107@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=randy.dunlap@oracle.com \
    --cc=tobias.oed@octant-fr.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