undefined reference to xenpci_alloc_space
Hi List, is it intended that kernel does not build if device xenpci is omitted in the kernel config? I get the following error: linking kernel gnttab.o: In function `gnttab_resume': /usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to `xenpci_alloc_space' Thanks, Michael ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: undefined reference to xenpci_alloc_space
On Oct 10, 2013, at 12:40 PM, Michael Schmiedgen wrote: > Hi List, > > is it intended that kernel does not build if > > device xenpci > > is omitted in the kernel config? I get the following error: > > linking kernel > gnttab.o: In function `gnttab_resume': > /usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to > `xenpci_alloc_space' > > Thanks, > Michael > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > XENHVM depends on xenpci, so you must remove XENHVM if you remove xenpci. Perhaps we should make a change similar to the attached patch in order to make this clear? -- Justin GENERIC.diff Description: Binary data ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: undefined reference to xenpci_alloc_space
On 10/11/13 05:39, Justin T. Gibbs wrote: On Oct 10, 2013, at 12:40 PM, Michael Schmiedgen wrote: is it intended that kernel does not build if device xenpci is omitted in the kernel config? I get the following error: linking kernel gnttab.o: In function `gnttab_resume': /usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to `xenpci_alloc_space' Thanks, Michael XENHVM depends on xenpci, so you must remove XENHVM if you remove xenpci. Perhaps we should make a change similar to the attached patch in order to make this clear? Arghh, my fault. I did not inspect changes to kernel config carefully enough. Thanks for the hint. Michael ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
