public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-acpi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	sam@ravnborg.org
Subject: Re: Fwd: Re: Linux 2.6.22-rc1
Date: Wed, 16 May 2007 00:42:08 +0900	[thread overview]
Message-ID: <20070515154208.GJ5043@inferi.kami.home> (raw)
In-Reply-To: <20070514104546.10a4368f.randy.dunlap@oracle.com>

On Mon, May 14, 2007 at 10:45:46AM -0700, Randy Dunlap wrote:
> On Mon, 14 May 2007 07:49:31 +0200 (MEST) Jan Engelhardt wrote:
> 
> > 
> > On May 14 2007 10:55, Mattia Dongili wrote:
> > >On Sun, May 13, 2007 at 11:27:31AM +0200, Jan Engelhardt wrote:
> > >> On May 12 2007 20:20, Linus Torvalds wrote:
> > >> >
> > >> >Ok, the merge window has closed, and 2.6.22-rc1 is out there.
> > >> 
> > >> I have hit a randconfig compile failure. .config attached.
> > >> 
> > >>   LD      .tmp_vmlinux1
> > >> drivers/built-in.o: In function `acpi_bus_generate_event':
> > >> (.text+0x233f7): undefined reference to `event_is_open'
> > >> drivers/built-in.o: In function `acpi_bus_get_power':
> > >> (.text+0x236ad): undefined reference to `acpi_power_get_inferred_state'
> > >> drivers/built-in.o: In function `acpi_bus_set_power':
> > >> (.text+0x237c3): undefined reference to `acpi_power_transition'
> > >> drivers/built-in.o: In function `acpi_bus_set_power':
> > >> (.text+0x23835): undefined reference to `acpi_power_transition'
> > >> drivers/built-in.o: In function `sony_pic_fanspeed_store':
> > >> sony-laptop.c:(.text+0x91930): undefined reference to `ec_write'
> > >> drivers/built-in.o: In function `sony_pic_fanspeed_show':
> > >> sony-laptop.c:(.text+0x9195d): undefined reference to `ec_read'
> > >> make: *** [.tmp_vmlinux1] Error 1
> > >
> > >I actually can't reproduce it with your .config.
> > 
> > But I can. Did you try it on x86_64? From 2.6.22-rc1 [
> > commit 39403865d2e4590802553370a56c9ab93131e4ee in /linux-2.6.git] ?
> > 
> > 	bzip2 -cd randconfig-1.bz2 >.config
> > 	make -j8
> 
> Yes, build easily fails for me also.

ok, as far as sony-laptop is concerned a dependency on ACPI_EC suffices
to fix the link failure, but I guess that would just hide the real
issue.
IOW: why does ACPI_EC, ACPI_SYSTEM and ACPI_POWER are not set when the
ACPI symbol is?

Given the drivers/acpi/Kconfig portion

  if ACPI
  ...
  config ACPI_EC
          bool
          default y
          help
            ...
  
  config ACPI_POWER
          bool
          default y
  
  config ACPI_SYSTEM
          bool
          default y
          help
	  ...
  ...
  endif

I'd expect the 3 symbols to be all set when CONFIG_ACPI=y.
What am I overseeing?

-- 
mattia
:wq!

  reply	other threads:[~2007-05-15 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13  9:27 Fwd: Re: Linux 2.6.22-rc1 Jan Engelhardt
2007-05-14  1:55 ` Mattia Dongili
2007-05-14  5:49   ` Jan Engelhardt
2007-05-14 17:45     ` Randy Dunlap
2007-05-15 15:42       ` Mattia Dongili [this message]
2007-05-15 17:46         ` Randy Dunlap
2007-05-16  2:41           ` Mattia Dongili

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=20070515154208.GJ5043@inferi.kami.home \
    --to=malattia@linux.it \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.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