Date: Wed, 1 Jun 2016 17:06:17 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: 11.0 -r301139: WITH_META_MODE=yes vs. "sh: ./make_keys: Exec format error"? Message-ID: <3f46eda7-0e66-a113-6f85-24f9c3fc4f4f@FreeBSD.org> In-Reply-To: <943D8647-5894-4E6D-AB49-02EAF39433F4@dsl-only.net> References: <890D3808-1939-4BEA-886F-324EBA8C8671@dsl-only.net> <0b75f448-047f-53b3-3e1b-7de17a2da949@FreeBSD.org> <a44a4e58-9cd3-f731-cbd8-f6b4ed55f5f3@FreeBSD.org> <943D8647-5894-4E6D-AB49-02EAF39433F4@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --V6SLpJdpfj6pwX7ETuntmIEfJkFMDxVmk Content-Type: multipart/mixed; boundary="09RPEgfqTInCHEmNli4LxnTwqeXafsv8H" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Message-ID: <3f46eda7-0e66-a113-6f85-24f9c3fc4f4f@FreeBSD.org> Subject: Re: 11.0 -r301139: WITH_META_MODE=yes vs. "sh: ./make_keys: Exec format error"? References: <890D3808-1939-4BEA-886F-324EBA8C8671@dsl-only.net> <0b75f448-047f-53b3-3e1b-7de17a2da949@FreeBSD.org> <a44a4e58-9cd3-f731-cbd8-f6b4ed55f5f3@FreeBSD.org> <943D8647-5894-4E6D-AB49-02EAF39433F4@dsl-only.net> In-Reply-To: <943D8647-5894-4E6D-AB49-02EAF39433F4@dsl-only.net> --09RPEgfqTInCHEmNli4LxnTwqeXafsv8H Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 6/1/2016 4:48 PM, Mark Millard wrote: > On 2016-Jun-1, at 4:30 PM, Bryan Drewery <bdrewery at FreeBSD.org> wrot= e: >=20 >> 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 -> armv= 6 cross build.] >>>> >>>> In my recent experimentation with WITH_META_MODE=3Dyes I=E2=80=99ve = 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=E2=80=99ve also had such for powerpc being the target and make too= lchain in use (preparing for buildkernel without buildworld). >>>> >>>> There are multiple instances of make_keys construction in the builds= =2E Here it looks like: >>>>> # grep make_keys ~/sys_typescripts/typescript_make_rpi2_nodebug_cla= ng_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 l= isted. >>>> >>>> cleanworld and then retrying the sequence desired always seems to wo= rk 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 buil= d >>> tests. >>> >> >> It's possible r301079 reintroduced the bug. I'll find out. >> >> --=20 >> Regards, >> Bryan Drewery >=20 > [All the below is from an amd64 host context.] >=20 > As far as I remember I've not seen "sh: ./make_keys: Exec format error"= when powerpc64-gcc or amd64-gcc is in use (my xtoolchain experiments): m= y src.conf files for such have more in them and various other differences= for those because of binding to powerpc64-gcc or amd64-gcc and the relat= ed binutils. >=20 > [The below do not involve ports compilers/tools.] >=20 > I have seen "sh: ./make_keys: Exec format error" when clang or gcc 4.2.= 1 is being used for the cross compiles. My armv6 context has a clang base= d buildworld and buildkernel. My powerpc kernel builds have a gcc 4.2.1 b= ased buildkernel (no buildworld). >=20 > I've not seen the problem for amd64 targeting amd64 via clang as far as= I can remember. I've not tried WITH_META_MODE=3Dyes for any other self-t= argeting context yet. >=20 Yup it is due to r301079. Will have to think on this. It was a temporary workaround until bmake was fixed. --=20 Regards, Bryan Drewery --09RPEgfqTInCHEmNli4LxnTwqeXafsv8H-- --V6SLpJdpfj6pwX7ETuntmIEfJkFMDxVmk 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 iQEcBAEBAgAGBQJXT3h5AAoJEDXXcbtuRpfPa8cH/3WMfGlKu+UP8DqAJMxTrl9n EGaBpGaFATI2DmwYUtEjBFNFBLTZwdYfIIkw8GXx/mN57RHCAB5PiCY4O5T0zCmV hZRbipL69JrEcb5L6N35EDyxU6lZft41iXe9+FDa7OBmHrag8nChW47DBfJqFT7n ly9MzBmVep28q3DAZat6kZ5PjIeYKIyhbmZSddMq+WFOJIKPtXmKN1p6bvsLgYVD UTuX0/Wf0z6VKQmpuwndUrANIWT/5vAwmaM0yTgw2Z++zSmQb0CYGsCwp3XOeSXb qV4zwWkqx4rDJpvXDi0ZtS8PfifSnq3Mpsv9FcoEuZEo9AUEljTlJQw9o/duqYU= =/p19 -----END PGP SIGNATURE----- --V6SLpJdpfj6pwX7ETuntmIEfJkFMDxVmk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3f46eda7-0e66-a113-6f85-24f9c3fc4f4f>