From owner-freebsd-stable@freebsd.org Mon Oct 21 16:05:21 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7453815B0F6 for ; Mon, 21 Oct 2019 16:05:21 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46xhLT2D6Rz4Qgg; Mon, 21 Oct 2019 16:05:21 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id EA8C8E1C7; Mon, 21 Oct 2019 16:05:20 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Mon, 21 Oct 2019 16:05:18 +0000 From: Glen Barber To: Dimitry Andric Cc: Jeremy , freebsd-stable stable Subject: Re: Is it necessary to bump target triple for lib32 Message-ID: <20191021160518.GA1430@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2019 16:05:21 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 20, 2019 at 12:39:29AM +0200, Dimitry Andric wrote: > On 19 Oct 2019, at 05:51, Jeremy wrote: > >=20 > > While I was doing a buildworld for FreeBSD 12 stable (r353745) for amd6= 4, I > > noticed the target triple was set at x86_64-unknown-freebsd12.0 while it > > was building the 32 bit libraries. I was wondering if it was necessary = to > > bump it to 12.1 now that 12.1 is getting ready for release, or if it > > doesn't matter either way. I believe the relevant commit was from > > (r338268). In any case, buildworld completed with no issues. > >=20 > > If it's not necessary, sorry for the noise. >=20 > You are right, this is coming from Makefile.libcompat: >=20 > $ grep freebsd12 Makefile.libcompat > LIB32CPUFLAGS+=3D -target x86_64-unknown-freebsd12.0 > LIB32CPUFLAGS=3D -target mipsel-unknown-freebsd12.0 > LIB32CPUFLAGS=3D -target mips-unknown-freebsd12.0 >=20 > Glen, I think you have a list somewhere of the files that need to have > their versions bumped for releng branches, could you please add > Makefile.libcompat to it too? >=20 Yes, I will add it to the doc now. I thought it was there already, but apparently not. > Maybe at one point we should have one source of truth for that obtaining > that version number... :) >=20 We do have one. % make -C release -V REVISION 12.1 Glen --17pEHd4RhPHOinZp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl2t1zoACgkQAxRYpUeP 4pNyHg/9Eh7i62F1I3I87dhRihAzK4LM/rq9Yc4mEwLctmn7neCP/DKgkR2bBeXY YgH420OjFCOYaRD6wSv3XPCYyB4zTQdrRhQvKjLmoB0HAR3J6JOBjoTNvN2eSLMN QfmwUV5oHWNgZuhPjUjOmlKW+v4WKApYJROswDRk8bI3EGudWg6vwJgtauAr0lyf eyBujYaEVIpof2vfJV7JPi+ND2KiyUw1Q4Vs7KwCSGLMSdxE5xS4n+8ZAonLg9It MOBoXMbHD3y6KS89UGa0szIUhXDAfBVLQFuyqLL8uAzSWFZ7Lv3516SpmaN5CKFc uqrec+UruGeT0JdQOAYkgXGGPwHuVua/btp/DmEtSAQ3oteNhjUzxkzjc6jIbBKT sn75G5XUNHxNwInoGJYv9nAvvHpPn1r0OvEB9grBrdUEYiqDgUk50hXxcEDHto0/ 4JhXcs+TeqjqLVjKr+8C+jMFif/YiJT60X7KUNWpJIc7WGU/wwo6oEB3rDCd0Acl nfBXAe54Zgj8rHP4tQWtXkmUNshvAp6iWLktYi6Hw/x3NaWAuQRjZDBh+tkXPwVC BVpUPuSfm3HEkj2XHV8XCUOjY7Wc1+XXLteLocEhvoAqxtScnqZJa+ROA98QE9ZJ i0wmrdjMXEbDBYHNg1puhBpLl0i27qYcu7otOco/xfmSJ44Kcho= =XyMT -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--