Re: buildkernel broken after r326553

On 12/5/2017 9:10 AM, Bryan Drewery wrote:
> On 12/5/2017 9:03 AM, Yuri Pankov wrote:
>> Hi,
>>
>> Looks like one of the commits by Bryan (r326549-r326553) has broken the
>> kernel build for me (using -j32, but serial build did fail as well) --
>> checking out r326547 make it work again.
>>
>> I can't pinpoint the exact error in the build log, as it seems to be
>> some make weirdness, so here's a guess, please let me know if you need
>> full build log:
>>
>> --- all_subdir_vmm ---
>> make[4]: Graph cycles through `vmx_assym.h'
>> make[4]: Graph cycles through `vmx_genassym.o'
>> make[4]: Graph cycles through `svm_assym.h'
>> make[4]: Graph cycles through `svm_genassym.o'
>> `svm_genassym.c' is up to date.
>> `vmx_genassym.c' is up to date.
>> `vmm.c' is up to date.
>> `vmm_dev.c' is up to date.
>> `vmm_host.c' is up to date.
>> `vmm_instruction_emul.c' is up to date.
>> `vmm_ioport.c' is up to date.
>> `vmm_lapic.c' is up to date.
>> `vmm_mem.c' is up to date.
>> `vmm_stat.c' is up to date.
>> `vmm_util.c' is up to date.
>> `x86.c' is up to date.
>> `iommu.c' is up to date.
>> `ppt.c' is up to date.
>> `vatpic.c' is up to date.
>> `vatpit.c' is up to date.
>> `vhpet.c' is up to date.
>> `vioapic.c' is up to date.
>> `vlapic.c' is up to date.
>> `vpmtmr.c' is up to date.
>> `vrtc.c' is up to date.
>> `ept.c' is up to date.
>> `vmcs.c' is up to date.
>> `vmx_msr.c' is up to date.
>> `vmx_support.S' is up to date.
>> `vmx.c' is up to date.
>> `vtd.c' is up to date.
>> `vmcb.c' is up to date.
>> `svm.c' is up to date.
>> `svm_support.S' is up to date.
>> `npt.c' is up to date.
>> `ivrs_drv.c' is up to date.
>> `amdvi_hw.c' is up to date.
>> `svm_msr.c' is up to date.
>> `afterdepend' was not built (made 1, flags 2019, type 3018001)!
>>     `afterdepend' has .ORDER dependency against .depend (made 1, flags
>> 301b, type 3020001)
>> `opt_global.h' was not built (made 0, flags 2009, type 3000000)!
>> *** [all_subdir_vmm] Error code 1
> 
> I'll have a fix in shortly. Sorry about that.
> 

Fixed in r326569.

-- 
Regards,
Bryan Drewery