Date: Fri, 23 May 2014 17:29:48 -0600 From: Warner Losh <imp@bsdimp.com> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, Glen Barber <gjb@FreeBSD.org>, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Nathan Whitehorn <nwhitehorn@freebsd.org> Subject: Re: svn commit: r266553 - head/release/scripts Message-ID: <C5A59513-AF58-4749-BCD7-F54BB6F56E90@gmail.com> In-Reply-To: <20140523162020.GG72340@ivaldir.etoilebsd.net> References: <201405221922.s4MJM4Y9025265@svn.freebsd.org> <537F6706.6070509@freebsd.org> <20140523153619.GF72340@ivaldir.etoilebsd.net> <537F6EBC.3080008@freebsd.org> <20140523162020.GG72340@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 23, 2014, at 10:20 AM, Baptiste Daroussin <bapt@FreeBSD.org> = wrote: > On Fri, May 23, 2014 at 08:52:28AM -0700, Nathan Whitehorn wrote: >> On 05/23/14 08:36, Baptiste Daroussin wrote: >>> On Fri, May 23, 2014 at 08:19:34AM -0700, Nathan Whitehorn wrote: >>>> Is there any chance of finally switching the pkg abi identifiers to = just >>>> be uname -p? >>>> -Nathan >>> Keeping asking won't make it happen, I have explained a large number = of time why it >>> happened, why it is not easy for compatibility and why uname -p is = still not >>> representing the ABI we do support, and what flexibility we need = that the >>> current string offers to us. >>>=20 >>> if one is willing to do the work, please be my guess, just dig into = the archives >>> and join the pkg development otherwise: no it won't happen before a = while >>> because we have way too much work on the todo and this item is = stored at the >>> very end of this todo. >>>=20 >>> regards, >>> Bapt >>=20 >> I'm happy to do the work, and have volunteered now many times. If = uname=20 >> -p does not describe the ABI fully, then uname -p needs changes on = the=20 >> relevant platforms. Which are they? What extra flexibility does the=20= >> string give you if uname -p describes the ABI completely? >> -Nathan >=20 > just simple examples in armv6: > - eabi vs oabi > - The different float abi (even if only one is supported for now = others are > being worked on) > - little endian vs big endian All of those are encoded in the MACHINE_ARCH + freebsd version, no = exceptions on supported architectures that are tier 2 or higher. This seems like a = weak reason. > the extras flexibilit is being able to say this binary do support = freebsd i386 > and amd64 in one key, freebsd:9:x86:*, or or all arches freebsd:10:* Will there be a program to convert this new, special invention to the = standard that we=92ve used for the past 20 years? If you need the flexibility, = which I=92m not entirely sure I=92ve seen a good use case for. When would you have a x86 = binary package? Wouldn=92t it be either i386 or amd64? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C5A59513-AF58-4749-BCD7-F54BB6F56E90>