On 6/1/2016 4:29 PM, Bryan Drewery wrote: > On 6/1/2016 4:25 PM, Mark Millard wrote: >> [The example context here for extracted materials is a amd64 -> armv6 cross >> build.] >> >> In my recent experimentation with WITH_META_MODE=yes I’ve had multiple >> occasions when after updating /usr/src I attempt buildworld buildkernel and >> end up with something like: >>> --- lib/ncurses/ncursesw__L --- >>> Building /usr/obj/clang/arm.armv6/usr/src/lib/ncurses/ncursesw/init_keytry.h >>> --- init_keytry.h --- >>> sh: ./make_keys: Exec format error >>> *** [init_keytry.h] Error code 126 >>> >>> make[4]: stopped in /usr/src/lib/ncurses/ncursesw >>> 1 error >>> >>> make[4]: stopped in /usr/src/lib/ncurses/ncursesw >>> *** [lib/ncurses/ncursesw__L] Error code 2 >> I’ve also had such for powerpc being the target and make toolchain in use >> (preparing for buildkernel without buildworld). >> >> There are multiple instances of make_keys construction in the builds. Here >> it looks like: >>> # grep make_keys >>> ~/sys_typescripts/typescript_make_rpi2_nodebug_clang_bootstrap-amd64-host-2016-06-01:15:17:28 >>> Building /usr/obj/clang/arm.armv6/usr/src/lib/ncurses/ncursesw/make_keys >>> Building /usr/obj/clang/arm.armv6/usr/src/lib/ncurses/ncurses/make_keys >>> Building /usr/obj/clang/arm.armv6/usr/src/lib/ncurses/ncursesw/make_keys >>> sh: ./make_keys: Exec format error >> Note that ncursesw has two Building lines above with the same path listed. >> >> cleanworld and then retrying the sequence desired always seems to work but >> is a complete rebuild. > > I don't understand why you're hitting this. It's an issue that I ran > into and fixed and haven't run into again from several powerpc64 build > tests. >
It's possible r301079 reintroduced the bug. I'll find out. -- Regards, Bryan Drewery
signature.asc
Description: OpenPGP digital signature
