Date: Tue, 5 Dec 2017 09:10:03 -0800 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Yuri Pankov <yuripv@gmx.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: buildkernel broken after r326553 Message-ID: <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> In-Reply-To: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> References: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Fq1fwM0NxmHTsRuIlCd5h6NGfhHjvpRaA Content-Type: multipart/mixed; boundary="XRdVnK4Ik1wrrRrs7mlromOIRGCXUk7Mv"; protected-headers="v1" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Yuri Pankov <yuripv@gmx.com>, freebsd-current <freebsd-current@freebsd.org> Message-ID: <248e3651-0fed-0ebc-afaa-0e874572ee25@FreeBSD.org> Subject: Re: buildkernel broken after r326553 References: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> In-Reply-To: <3dd22d0b-130a-5eac-e64a-92add802694d@gmx.com> --XRdVnK4Ik1wrrRrs7mlromOIRGCXUk7Mv Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 12/5/2017 9:03 AM, Yuri Pankov wrote: > Hi, >=20 > 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. >=20 > 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: >=20 > --- 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)! > =C2=A0=C2=A0=C2=A0 `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. --=20 Regards, Bryan Drewery --XRdVnK4Ik1wrrRrs7mlromOIRGCXUk7Mv-- --Fq1fwM0NxmHTsRuIlCd5h6NGfhHjvpRaA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJaJtLrAAoJEDXXcbtuRpfPtJUIAJxHxCjVuYK2rRHM5LIj4zy0 MndqDLnRMOydxtEvSHElUJybC4J+OwcPG73PshcFUrHKlF3ef9s7LG1cIvbhjXwi rYRRERzOOl5QJHU/6/eSoPDaY5gmtB+OrNkBMuI2NopFZPo6GYVPfVA9iIRoU/mf mQOYnuOKArxCq9Vpq1FHnd+1LyjMzUWACN52FgPU+5hgbTZuuPbkHe7IKsQhLZ/7 BOUSXYtkHRXfSu7YfJN9Lij4soICyesKpG3Xh4mlbvk+sGnFz4R+moyN6PiaCka2 GOg7s64+mGUpSPan+fjdzf/6kbYgni0idFrMWNtKIYCafgnMjm7omtPipl2Zndk= =Sp1D -----END PGP SIGNATURE----- --Fq1fwM0NxmHTsRuIlCd5h6NGfhHjvpRaA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?248e3651-0fed-0ebc-afaa-0e874572ee25>