All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Quadriplegic Leprechaun <quadriplegic_leprechaun@ukonline.co.uk>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: 2.6.12-mm1: PCI compile error with CONFIG_HOTPLUG=n
Date: Fri, 24 Jun 2005 11:24:54 +0200	[thread overview]
Message-ID: <20050624092454.GE26545@stusta.de> (raw)
In-Reply-To: <42BBBBC0.2050702@ukonline.co.uk>

On Fri, Jun 24, 2005 at 08:52:32AM +0100, Quadriplegic Leprechaun wrote:

> Hi,

Hi,

> With the attached config, I get an undefined symbol error when building 
> the following kernel:
> 
> $ head Makefile
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 12
> EXTRAVERSION = -mm1
> NAME=Woozy Numbat
> 
> And this is the error I get:
> [ ... lots of output snipped ... ]
>  LD      vmlinux
> arch/i386/pci/built-in.o(.init.text+0x101e): In function `pcibios_init':
> common.c: undefined reference to `pci_assign_unassigned_resources'
> make: *** [vmlinux] Error 1

thanks for this report.

@Ivan, Greg:
gregkh-pci-pci-assign-unassigned-resources.patch breaks compilation with 
CONFIG_HOTPLUG=n.

> Quad

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:[~2005-06-24  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24  7:52 [2.6.12-mm1]: Undefined symbols Quadriplegic Leprechaun
2005-06-24  9:24 ` Adrian Bunk [this message]
2005-06-24 16:39   ` 2.6.12-mm1: PCI compile error with CONFIG_HOTPLUG=n Greg KH

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=20050624092454.GE26545@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quadriplegic_leprechaun@ukonline.co.uk \
    /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.