From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: acpi-devel@lists.sourceforge.net
Cc: Adam Litke <agl@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [ACPI] 2.6.14-rc4 ACPI/PCI compile problem
Date: Tue, 11 Oct 2005 17:17:01 -0600 [thread overview]
Message-ID: <200510111717.01887.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1129069727.27663.8.camel@localhost.localdomain>
On Tuesday 11 October 2005 4:28 pm, Adam Litke wrote:
> Ok I'll admit I've known about this since at least 2.6.14-rc2-git5 but
> it may have been around longer. Long enough for me to speak up.
>
> I am getting the following compile errors when building 2.6.14-rc4 for
> i386:
>
> > LD .tmp_vmlinux1
> > drivers/built-in.o(.text+0x235f9): In function `acpi_pci_root_add':
> > /home/aglitke/views/acpi-compile-fix-2.6.14-rc4/current/drivers/acpi/pci_root.c:274: undefined reference to `pci_acpi_scan_root'
> > make[1]: *** [.tmp_vmlinux1] Error 1
> > make: *** [_all] Error 2
Please try the following patch and confirm whether it works.
[i386 kbuild] Don't clobber pci-y when X86_VISWS or X86_NUMAQ
Previously, enabling CONFIG_X86_VISWS or CONFIG_X86_NUMAQ
clobbered any previous contents of pci-y, because they used
":=" instead of "+=".
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
diff -r ed3231e577f5 arch/i386/pci/Makefile
--- a/arch/i386/pci/Makefile Tue Oct 11 19:03:47 2005
+++ b/arch/i386/pci/Makefile Tue Oct 11 15:47:09 2005
@@ -8,7 +8,7 @@
pci-$(CONFIG_ACPI) += acpi.o
pci-y += legacy.o irq.o
-pci-$(CONFIG_X86_VISWS) := visws.o fixup.o
-pci-$(CONFIG_X86_NUMAQ) := numa.o irq.o
+pci-$(CONFIG_X86_VISWS) += visws.o fixup.o
+pci-$(CONFIG_X86_NUMAQ) += numa.o irq.o
obj-y += $(pci-y) common.o
next prev parent reply other threads:[~2005-10-11 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 22:28 Adam Litke
2005-10-11 23:17 ` Bjorn Helgaas [this message]
2005-10-12 14:34 ` [ACPI] " Adam Litke
2005-10-12 18:00 ` Matthew Wilcox
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=200510111717.01887.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=agl@us.ibm.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®