Date: Tue, 27 May 2014 07:18:06 -0600 From: Warner Losh <imp@bsdimp.com> To: Tijl Coosemans <tijl@FreeBSD.org> Cc: Baptiste Daroussin <bapt@freebsd.org>, src-committers@freebsd.org, Ian Lepore <ian@freebsd.org>, svn-src-all@freebsd.org, Glen Barber <gjb@freebsd.org>, Nathan Whitehorn <nwhitehorn@freebsd.org>, svn-src-head@freebsd.org Subject: Re: svn commit: r266553 - head/release/scripts Message-ID: <85FABD2B-81BB-4E1A-B61E-4216A144A9DB@bsdimp.com> In-Reply-To: <20140527093633.0a922e13@kalimero.tijl.coosemans.org> References: <201405221922.s4MJM4Y9025265@svn.freebsd.org> <537F6706.6070509@freebsd.org> <20140523153619.GF72340@ivaldir.etoilebsd.net> <537F6EBC.3080008@freebsd.org> <20140523162020.GG72340@ivaldir.etoilebsd.net> <C5A59513-AF58-4749-BCD7-F54BB6F56E90@gmail.com> <20140524165940.3c687553@kalimero.tijl.coosemans.org> <5380C311.60201@freebsd.org> <20140524185345.263f230d@kalimero.tijl.coosemans.org> <1400955835.1152.323.camel@revolution.hippie.lan> <5380EBA8.1030200@freebsd.org> <20140525011307.142b41ab@kalimero.tijl.coosemans.org> <3CCAFAD3-FABE-40EF-ABF9-815FE5826349@bsdimp.com> <9FE34CE4-C71F-4806-9EF6-30CB1051C62F@bsdimp.com> <20140526113502.239db74d@kalimero.tijl.coosemans.org> <5383522F.30108@freebsd.org> <DAD3E386-6555-4C43-9BBA-F3BFD28CC19B@bsdimp.com> <20140527001811.3e9d3e8d@kalimero.tijl.coosemans.org> <05D1A11D-5985-42EA-84AD-209A8B51D391@bsdimp.com> <20140527093633.0a922e13@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_97317F85-FC5E-4184-AFD6-7818C9A6F3CC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1253 On May 27, 2014, at 1:36 AM, Tijl Coosemans <tijl@FreeBSD.org> wrote: > On Mon, 26 May 2014 16:31:21 -0600 Warner Losh wrote: >> On May 26, 2014, at 4:18 PM, Tijl Coosemans <tijl@FreeBSD.org> wrote:=20= >>> On Mon, 26 May 2014 09:53:57 -0600 Warner Losh wrote: >>>> On May 26, 2014, at 8:39 AM, Nathan Whitehorn = <nwhitehorn@freebsd.org> wrote: >>>>> On 05/26/14 02:35, Tijl Coosemans wrote: >>>>>> I suppose you could replace the "x86" in the pkg scheme with = i386/amd64, >>>>>> but then you'd still be talking about i386:32, amd64:32 and = amd64:64 >>>>>> instead of x86:32, x86:x32 and x86:64. =20 >>>>=20 >>>> I suppose you could replace these by =93i386=94, =93x32=94 (or = =93amd64x32=94) and >>>> =93amd64=94 respectively. >>>=20 >>> So you're on an amd64 or mips64 system (as indicated by uname) but = you >>> want to use the 32-bit package if possible. How does your script = know >>> about the magic "x32", "amd64x32" or "mipsn32" strings? Wouldn't it = be >>> easier if you could just use "`uname -p`:32=94? >>=20 >> Oh give me a break. You know it because you know you are building for >> mipsn32 because that=92s what you=92ve set MACHINE_ARCH or = TARGET_ARCH to, >=20 > No, MACHINE_ARCH or TARGET_ARCH is "amd64" or "mips64". You are = building > the 64-bit OS and then decide separately per package whether you want = the > ILP32 one or the LP64 one. I think I understand why we=92re talking past each other. This bit is = wrong. The LP64 one has a MACHINE_ARCH of =93amd64=94 or =93mips64=94. = The ILP32 one will have MACHINE_ARCH of =93i386=94 or =93mips=94. The = weird ones (ILP32 with 64-bit registers) will have a different = MACHINE_ARCH of =93x32=94 or =93mipsn32=94. Selection can be done on a = case by case basis, but this will be validated against the = supported_abis sysctl. There=92s no need to have different names here, = the current standard ones do just fine, are completely sufficient and = all inclusive. This is rather by definition, and your understanding of = the definition sounds flawed. While we have limited support for building 32-bit binaries, it is to = build 32-bit binaries for a different MACHINE_ARCH. -m32 on amd64 = creates i386 binaries, not amd64:32 binaries. -m32 on powerpc64 creates = powerpc binaries, not powerpc64:32 binaries. On mips, -mabi-n32 (I think = the option is) is required to create the mipsn32 binaries. In every = single one of these cases, there exists a MACHINE_ARCH that completely = describes the binary. So I=92m still waiting for a use case that requires the new names. One = has not been articulated, and I don=92t think one actually exists. Warner --Apple-Mail=_97317F85-FC5E-4184-AFD6-7818C9A6F3CC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJThJCOAAoJEGwc0Sh9sBEA00YP+gPTsPiS2QcuZukJLG6wKhLz NPOIA2zgXl8dS9iYq/bf9uRxiYW6p2C68gmzTjxn0K3bYm/oFTTA8ZaLoaNQ4iqu /7Qk6aMkGcTiUpSPZE+Bnc8LMO6lvHQWdBJ7gBuGKMRaSTR4jN+7O5MnvLtkBthP D98Y19r44BNsvVxVwPPOzz3Vf2i8ivsn78PHngE1xfvHcCQKShnVr+uFPHmFSePX 4HHs5kaV/MWS7791Lisnr3KW5EjQmS+3DkDi8Rhtj8Jm+quak1OVwxzd8bIj6HDs /c94j/B2F0X7kch3SVIaJBPjrMLbdufkwjw/JR7PcboszgMpfYa4isDFH9DG18Xf E40O00voBQzouo2kV10STJV4UTx+3Qxm6hLt5A6aqDSL08NzXsMnxjE5lSNt8jNW 3uheHp1JLqoHt6/IcAxvc7SiVMgNn1Xu2w507cLlkvE4eM9Xspy0dueJ/Bm7xuup M9GUZOcGpLQTnEeyHUBwJyov5tLrZyzkKWaJdGloi1pV+zWGDlHaoeu7yUMwNaWd Wwb+e3S0/4oNyFDEdQSgXZdVgJiNcHDgQWzY1aeVt887rfTQ1tNe2R4CC+4mZClf bID4wFz0pfGBUUSD4j+li9fMhvES5IUj8aRVpmiDvqQkrxBWPLxakFI7MI+kj0EQ yuAwurHmTDbTq+w9Nnee =0KJ6 -----END PGP SIGNATURE----- --Apple-Mail=_97317F85-FC5E-4184-AFD6-7818C9A6F3CC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85FABD2B-81BB-4E1A-B61E-4216A144A9DB>