From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Linux-Kernel (E-mail)"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: 2.6.0-test7 build failure: !CONFIG_PCI
Date: 10 Oct 2003 23:43:05 -0400 [thread overview]
Message-ID: <1065843784.4112.49.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE001126CB1-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
Does anybody build X86 without CONFIG_PCI?
Build fails if CONFIG_BLK_DEV_CMD640 is set:
drivers/built-in.o(.init.text+0x59df): In function `ide_setup':
: undefined reference to `cmd640_vlb'
drivers/built-in.o(.init.text+0x5aef): In function `probe_for_hwifs':
: undefined reference to `ide_probe_for_cmd640x'
make: *** [.tmp_vmlinux1] Error 1
The problem is that these variables are defined in
drivers/ide/pci/cmd640.c, which is protected by CONFIG_PCI; but they're
used when CONFIG_BLK_DEV_CMD640, which doesn't require CONFIG_PCI.
---
More interesting (to me) is that it also fails if CONFIG_ACPI is set:
drivers/built-in.o(.init.text+0x825): In function `acpi_bus_init':
: undefined reference to `eisa_set_level_irq'
drivers/acpi/bus.c:
#ifdef CONFIG_X86
/* Ensure the SCI is set to level-triggered, active-low */
if (acpi_ioapic)
mp_config_ioapic_for_sci(acpi_fadt.sci_int);
else
eisa_set_level_irq(acpi_fadt.sci_int);
#endif
Should we not be calling eisa_set_level_irq()?
thanks,
-Len
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
WARNING: multiple messages have this Message-ID (diff)
From: Len Brown <len.brown@intel.com>
To: "Linux-Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Cc: acpi-devel@lists.sourceforge.net
Subject: 2.6.0-test7 build failure: !CONFIG_PCI
Date: 10 Oct 2003 23:43:05 -0400 [thread overview]
Message-ID: <1065843784.4112.49.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE001126CB1@hdsmsx402.hd.intel.com>
Does anybody build X86 without CONFIG_PCI?
Build fails if CONFIG_BLK_DEV_CMD640 is set:
drivers/built-in.o(.init.text+0x59df): In function `ide_setup':
: undefined reference to `cmd640_vlb'
drivers/built-in.o(.init.text+0x5aef): In function `probe_for_hwifs':
: undefined reference to `ide_probe_for_cmd640x'
make: *** [.tmp_vmlinux1] Error 1
The problem is that these variables are defined in
drivers/ide/pci/cmd640.c, which is protected by CONFIG_PCI; but they're
used when CONFIG_BLK_DEV_CMD640, which doesn't require CONFIG_PCI.
---
More interesting (to me) is that it also fails if CONFIG_ACPI is set:
drivers/built-in.o(.init.text+0x825): In function `acpi_bus_init':
: undefined reference to `eisa_set_level_irq'
drivers/acpi/bus.c:
#ifdef CONFIG_X86
/* Ensure the SCI is set to level-triggered, active-low */
if (acpi_ioapic)
mp_config_ioapic_for_sci(acpi_fadt.sci_int);
else
eisa_set_level_irq(acpi_fadt.sci_int);
#endif
Should we not be calling eisa_set_level_irq()?
thanks,
-Len
next parent reply other threads:[~2003-10-11 3:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE001126CB1@hdsmsx402.hd.intel.com>
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE001126CB1-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-10-11 3:43 ` Len Brown [this message]
2003-10-11 3:43 ` 2.6.0-test7 build failure: !CONFIG_PCI Len Brown
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=1065843784.4112.49.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.