From owner-freebsd-current@freebsd.org Wed Jun 1 23:48:47 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 113F7B66E12 for ; Wed, 1 Jun 2016 23:48:47 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-182.reflexion.net [208.70.211.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B9A1617AC for ; Wed, 1 Jun 2016 23:48:46 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 32738 invoked from network); 1 Jun 2016 23:49:10 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 1 Jun 2016 23:49:10 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.90.3) with SMTP; Wed, 01 Jun 2016 19:48:36 -0400 (EDT) Received: (qmail 7351 invoked from network); 1 Jun 2016 23:48:36 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 1 Jun 2016 23:48:36 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id CBEAE1C43E2; Wed, 1 Jun 2016 16:48:33 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: 11.0 -r301139: WITH_META_MODE=yes vs. "sh: ./make_keys: Exec format error"? From: Mark Millard In-Reply-To: Date: Wed, 1 Jun 2016 16:48:38 -0700 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <943D8647-5894-4E6D-AB49-02EAF39433F4@dsl-only.net> References: <890D3808-1939-4BEA-886F-324EBA8C8671@dsl-only.net> <0b75f448-047f-53b3-3e1b-7de17a2da949@FreeBSD.org> To: Bryan Drewery X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 23:48:47 -0000 On 2016-Jun-1, at 4:30 PM, Bryan Drewery = wrote: > 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.] >>>=20 >>> 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 >>>>=20 >>>> make[4]: stopped in /usr/src/lib/ncurses/ncursesw >>>> 1 error >>>>=20 >>>> 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 = toolchain in use (preparing for buildkernel without buildworld). >>>=20 >>> 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. >>>=20 >>> cleanworld and then retrying the sequence desired always seems to = work but is a complete rebuild. >>=20 >> 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. >>=20 >=20 > It's possible r301079 reintroduced the bug. I'll find out. >=20 > --=20 > Regards, > Bryan Drewery [All the below is from an amd64 host context.] 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): = my 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 related binutils. [The below do not involve ports compilers/tools.] 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 based = buildworld and buildkernel. My powerpc kernel builds have a gcc 4.2.1 = based buildkernel (no buildworld). 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-targeting context yet. =3D=3D=3D Mark Millard markmi at dsl-only.net