linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: linuxppc-dev@ozlabs.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: 2.6.29-rc6-git6 defconfig build failure
Date: Tue, 03 Mar 2009 15:20:06 +0530	[thread overview]
Message-ID: <49ACFD4E.8060506@in.ibm.com> (raw)

2.6.29-rc6-git6 ppc64_defconfig build fails with 

arch/powerpc/kernel/built-in.o: In function `.of_pci_phb_probe':
of_platform.c:(.devinit.text+0xe0): undefined reference to `.pcibios_claim_one_bus'
arch/powerpc/platforms/built-in.o: In function `.remove_phb_dynamic':
(.text+0x120fc): undefined reference to `.pcibios_unmap_io_space'
arch/powerpc/platforms/built-in.o: In function `.pcibios_add_pci_devices':
(.text+0x12338): undefined reference to `.pcibios_finish_adding_to_bus'
arch/powerpc/platforms/built-in.o: In function `.init_phb_dynamic':
(.devinit.text+0x6ec): undefined reference to `.pcibios_finish_adding_to_bus'
make: *** [.tmp_vmlinux1] Error 1

git5 did not have this problem as CONFIG_HOTPLUG was set with ppc64_defconfig.
With git6 defconfig there is no CONFIG_HOTPLUG

# grep CONFIG_HOTPLUG linux-2.6.29-rc6-git6/.config
# 

# grep CONFIG_HOTPLUG linux-2.6.29-rc6-git5/.config
CONFIG_HOTPLUG=y
CONFIG_HOTPLUG_CPU=y
CONFIG_HOTPLUG_PCI=m
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
CONFIG_HOTPLUG_PCI_RPA=m
CONFIG_HOTPLUG_PCI_RPA_DLPAR=m

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

             reply	other threads:[~2009-03-03  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  9:50 Sachin P. Sant [this message]
2009-03-03 11:50 ` 2.6.29-rc6-git6 defconfig build failure Michael Neuling

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=49ACFD4E.8060506@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).