No, VIMAGE should be pulled in from an existing configuration in your
compile/{KERNEL}/opt_global.h, right?
So why's the driver not pulling it in?
adrian
On 6 March 2012 13:53, Monthadar Al Jaberi <montha...@gmail.com> wrote:
> something like
> .if defined(KERNBUILDDIR)
> MKDEP= -include ${KERNBUILDDIR}/opt_global.h
> .else
> CFLAGS+= -include opt_global.h
> MKDEP= -include opt_global.h
>
> opt_global.h:
> echo "#define VIMAGE 1" > ${.TARGET}
> .endif
>
> ?
>
> On Tue, Mar 6, 2012 at 10:52 PM, Adrian Chadd <adrian.ch...@gmail.com> wrote:
>> On 6 March 2012 13:51, Marko Zec <z...@fer.hr> wrote:
>>> On Tuesday 06 March 2012 22:49:56 Adrian Chadd wrote:
>>>> Wait a sec. Is it possible that the macro is a no-op when we're
>>>> building modules w/ VNET?
>>>
>>> Yes that's it, the VNET stuff resolves (mostly) to whitespace when options
>>> VIMAGE is not on!
>>
>> So the question is - how the heck are the modules supposed to pull in
>> the VNET config?
>>
>> is there a missing opt_<x>.h somewhere?
>>
>>
>> Adrian
>
>
>
> --
> Monthadar Al Jaberi
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
