Should I attach my entire .config file in the future? It's large enough that
I try to trim it to avoid bloating people's inboxes.
Yes, that's right. It is compiled as a module. So this just needs
a tweaked config rule, right?
Thanks,
Miles
On 6/25/06, Adrian Bunk <bunk@xxxxxxxxx> wrote:
On Sun, Jun 25, 2006 at 12:56:44PM -0700, Miles Lane wrote:
> drivers/built-in.o: In function
> `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined
> reference to `is_dock_device'
> drivers/built-in.o: In function
> `cleanup_bridge':acpiphp_glue.c:(.text+0x12bc4): undefined reference
> to `is_dock_device'
> :acpiphp_glue.c:(.text+0x12bd3): undefined reference to
> `unregister_hotplug_dock_device'
> :acpiphp_glue.c:(.text+0x12bdb): undefined reference to
> `unregister_dock_notifier'
> drivers/built-in.o: In function
> `register_slot':acpiphp_glue.c:(.text+0x13ac0): undefined reference to
> `is_dock_device'
> :acpiphp_glue.c:(.text+0x13cd9): undefined reference to `is_dock_device'
> :acpiphp_glue.c:(.text+0x13cf0): undefined reference to
> `register_hotplug_dock_device'
> :acpiphp_glue.c:(.text+0x13d1d): undefined reference to
> `register_dock_notifier'
> make: *** [.tmp_vmlinux1] Error 1
>
> #
> # PCI Hotplug Support
> #
> CONFIG_HOTPLUG_PCI=y
> CONFIG_HOTPLUG_PCI_FAKE=y
> CONFIG_HOTPLUG_PCI_COMPAQ=y
> # CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
> CONFIG_HOTPLUG_PCI_ACPI=y
> CONFIG_HOTPLUG_PCI_ACPI_IBM=y
> CONFIG_HOTPLUG_PCI_CPCI=y
> # CONFIG_HOTPLUG_PCI_CPCI_ZT5550 is not set
> CONFIG_HOTPLUG_PCI_CPCI_GENERIC=y
> CONFIG_HOTPLUG_PCI_SHPC=y
> # CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set
You hadn't attached your complete .config, but is it correct when I
assume you have CONFIG_ACPI_DOCK=m? This would explain the problem.
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
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
