The release engineering team uses qemu-user-static for building arm64 VM images, and it has been failing to build recently: 3 warnings generated. 3 warnings generated. 1 warning generated. 3 warnings generated. gmake[2]: Leaving directory '/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-6ffee39fe2e4/arm-bsd-user' gmake[1]: *** [Makefile:483: subdir-arm-bsd-user] Error 2 gmake[2]: Leaving directory '/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-6ffee39fe2e4/aarch64-bsd-user' gmake[1]: *** [Makefile:483: subdir-aarch64-bsd-user] Error 2 gmake[2]: Leaving directory '/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-6ffee39fe2e4/mips64el-bsd-user' gmake[1]: *** [Makefile:483: subdir-mips64el-bsd-user] Error 2 gmake[2]: Leaving directory '/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-6ffee39fe2e4/sparc-bsd-user' gmake[1]: *** [Makefile:483: subdir-sparc-bsd-user] Error 2 gmake[2]: Leaving directory '/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-6ffee39fe2e4/ppc-bsd-user' gmake[1]: *** [Makefile:483: subdir-ppc-bsd-user] Error 2 gmake[1]: Leaving directory '/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-6ffee39fe2e4' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/emulators/qemu-user-static *** Error code 1
Since we (at present) only use this for arm64, I was wondering if it would make our lives easier to have a stripped-down and rarely-updated "qemu-user-releng" port.
I sent a request out-of-band for more of the log, since this excerpt didn't capture the failure. releng should already be using emulators/qemu-user-static, which doesn't see updates but once in a blue moon (last real update was in May) -- I don't think a separate port will do us much good, typical breakage is from base updates.
11:32 <@kevans91_> looks like some header change probably broke it 11:32 <@kevans91_> target_os_user.h is now pulling in sys/user.h and getting smacked by macro expansion of kve_vn_fsid
I'll take a look at this when I'm back on Tuesday (or maybe a little before)...
(In reply to Warner Losh from comment #4) We've had this error several times before...
I'll see if I can get to it this weekend. Given that re@ relies on qemu-user-static, we should really get a CI job in Jenkins going for base changes like this that break it. I don't know if re@ has other ports they'd like to add to that, but CC lwhsu@ to start the conversation. If re@ doesn't have anything else to add, then a job that builds qemu-user-static and notifies imp/kevans (please not the committers involved) on job failures would be fine.
I think this is fixed
(In reply to Warner Losh from comment #7) Yup, we've gotten qemu back out of the way; the latest failures were kld funkiness. Closing...