Date: Thu, 2 Jun 2016 11:52:29 -0700 From: Mark Millard <markmi@dsl-only.net> To: "Simon J. Gerraty" <sjg@juniper.net> Cc: Bryan Drewery <bdrewery@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: 11.0 -r301139: WITH_META_MODE=yes vs. "sh: ./make_keys: Exec format error"? Message-ID: <12D1F020-F1F1-464A-BAEA-18682E1ADA17@dsl-only.net> In-Reply-To: <92116.1464890038@kaos.jnpr.net> References: <890D3808-1939-4BEA-886F-324EBA8C8671@dsl-only.net> <92116.1464890038@kaos.jnpr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-Jun-2, at 10:35 AM, Simon J. Gerraty <sjg at juniper.net> wrote: > Mark Millard <markmi at dsl-only.net> wrote: >=20 >>>>>> Building = /usr/obj/clang/arm.armv6/usr/src/lib/ncurses/ncursesw/make_keys >>>>>> sh: ./make_keys: Exec format error >=20 > This is an arm host or cross-building? >=20 > The error suggests HOST_CC got the wrong value. > You should be able to look at >=20 > /usr/obj/clang/arm.armv6/usr/src/lib/ncurses/ncursesw/make_keys.meta >=20 > to confirm whether the right toolchain was used. Quoting what I originally wrote that has been dropped from the context = preserved in the recent list entries: > [The example context here for extracted materials is a amd64 -> armv6 = cross build.] On 2016-Jun-2, at 10:53 AM, Simon J. Gerraty <sjg at juniper.net> wrote: > BTW Mark, thanks very much for testing this. >=20 >>> # 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 >>=20 >> Note that ncursesw has two Building lines above with the same path = listed. >=20 > This build is still using the normal orchestration (tree walks etc) > so it it not at all out of the question for directories to be visited > more than once. >=20 > If curious; you can add -dM to have make explain why it built it again > the 2nd time. > The output can be copious, so you might want to only enable it in > ncursesw > eg. >=20 > .MAKEFLAGS: -dM You dropped the note where Bryan Drewery reported already having found = the problem: On 2016-Jun-1, at 5:06 PM, Bryan Drewery <bdrewery at FreeBSD.org> = wrote: > Yup it is due to r301079. Will have to think on this. It was a = temporary > workaround until bmake was fixed. >=20 >=20 > --=20 > Regards, > Bryan Drewery There is also the issue that installworld to / and reboot results in the = next buildworld buildkernel for each TARGET_ARCH being essentially a = complete build. ( = https://lists.freebsd.org/pipermail/freebsd-current/2016-June/061606.html = ) For my use this last usually removes the most of the potential time gain = from WITH_META_MODE=3Dyes. And taking less time is why I was = experimenting with using it. =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12D1F020-F1F1-464A-BAEA-18682E1ADA17>