public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Martin MOKREJ? <mmokrejs@ribosome.natur.cuni.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-rc3-git5: drivers/acpi/osl.c:57:38: empty filename in #include
Date: Fri, 17 Feb 2006 01:05:25 +0100	[thread overview]
Message-ID: <20060217000525.GD4422@stusta.de> (raw)
In-Reply-To: <43F3B553.2010506@ribosome.natur.cuni.cz>

On Thu, Feb 16, 2006 at 12:12:19AM +0100, Martin MOKREJ? wrote:

> Hi,

Hi Martin,

>   I have the following problem when compiling linux kernel on Intel 
> Pentium4M machine:
> 
> drivers/acpi/osl.c:57:38: empty filename in #include
> drivers/acpi/osl.c: In function `acpi_os_table_override':
> drivers/acpi/osl.c:258: error: `AmlCode' undeclared (first use in 
> this function)
> drivers/acpi/osl.c:258: error: (Each undeclared identifier is 
> reported only once
> drivers/acpi/osl.c:258: error: for each function it appears in.)
> make[2]: *** [drivers/acpi/osl.o] Error 1
> 
>   It turned out I have enabled the custom DSDT option but the field 
> for the custom file have left empty. That's the cause for the error.
> Something should probably take care of this case. I use "menuconfig"
> to manipulate the .config file.

this is a class of errors Kconfig can't handle.

And if it was handled, the next problems were to check first whether the 
file exists, and next whether it's actually a valid DSDT table file...

Kconfig helps you to avoid many errors, but there are classes of errors 
it simply can't prevent.

> M.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-02-17  0:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 23:12 2.6.16-rc3-git5: drivers/acpi/osl.c:57:38: empty filename in #include Martin MOKREJŠ
2006-02-17  0:05 ` Adrian Bunk [this message]
2006-02-17  0:11   ` Randy.Dunlap
2006-02-17  0:56     ` Adrian Bunk
2006-02-17  0:58       ` Randy.Dunlap
2006-02-17  1:30         ` Adrian Bunk
2006-02-17  9:12   ` Martin MOKREJŠ

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=20060217000525.GD4422@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    /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