Date: Wed, 10 Jul 2013 21:55:47 +0200 From: Baptiste Daroussin <bapt@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: Dimitry Andric <dim@freebsd.org>, Andrew Turner <andrew@fubar.geek.nz>, freebsd-arch@freebsd.org Subject: Re: Adding a MACHINE_ARCH note Message-ID: <20130710195547.GB68830@ithaqua.etoilebsd.net> In-Reply-To: <CAJ-Vmo=sUKs4u-pq%2B1hx-q1bfhPugMcSp4XYzNcBNwHMrw3Kug@mail.gmail.com> References: <32F979BD-FB5C-4111-9586-4C5E7C6DFA71@bsdimp.com> <20130709234837.559e3769@bender.Home> <CAJ-Vmo=iV8BsGriFRgNuP-ZJdQhpmBLhjAkz-nSVRS0HPKSyOQ@mail.gmail.com> <CAGE5yCpJmRDvnaYtozj4bCqNoQXH=1e96HPJAqwJuRdn4H9BZA@mail.gmail.com> <CAJ-Vmo=tmGDW3Ubw9nr5rb30bXr1dcJUkKLOU7L=_bx29zvEhw@mail.gmail.com> <CAGE5yCq9gQERDkbi4wu=6tNUap24ZR7sL7aF%2BzmEO0eT6nxPsA@mail.gmail.com> <F79E2F76-A234-499A-ABB7-1ABA62283E9D@FreeBSD.org> <CAJ-VmonwJJ7AtCTCDXGOW2k9RufCG3Vj0Tqy3DAO_wZb6cYg6Q@mail.gmail.com> <752588A3-C0EF-4844-A0EE-4657CAD40E4C@bsdimp.com> <CAJ-Vmo=sUKs4u-pq%2B1hx-q1bfhPugMcSp4XYzNcBNwHMrw3Kug@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 10, 2013 at 12:26:42PM -0700, Adrian Chadd wrote: > On 10 July 2013 09:55, Warner Losh <imp@bsdimp.com> wrote: >=20 > >> That's the reason I replied about it. Not specifically to make it > >> happen _everywhere_, but to see if we're about to migrate to a tool > >> that doesn't support it, making it a much bigger deal to migrate again > >> later. > > > > I've been talking to Baptiste, and it will support this. >=20 > Sweet. >=20 > Thanks! >=20 >=20 > -adrian Yeah I need to get a simple and uniq way to gather the different ABI, I have been creating my own ABI string to solve this, but I'm far from being a specialist. While thinking about this kind of thing, please please think about a format= that can easily give us a way to figure out a way to get cross ABI binaries supp= ort. pkgng needs for example to allow i386 packages to be installed on amd64 bec= ause amd64 does support it. Maintaining a list the compatibility will be painful. In my own version I have os:version:family:class:... for example here: on FreeBSD 9 i386 we have: freebsd:9:x86:32 on FreeBSD 10 amd64 we have: freebsd:9:x86:64 now if I do want a package I can install on both amd64 and i386 I just have= to create a package saying: freebsd:9:x86 or if I want a package that can be installed on all arches: freebsd:9 It became complicated for arm and mips because of the multiple variation available. the problem with that is that I have to read the binary supported from the binaries themselves which enforce me to get some magical numbers for every arches (which was apparently wrong on arm, thanks Andrew for the fix) Havin= g a note with the direct MACHINE_ARCH will save us complicated code and potenti= al failures with magic numbers. and would be more reliable that getting from uname(3). Just tell me where I can get the right string and how can I check the compa= tible ABI and pkgng will switch to it. I would have love this to happen a year an= d a half before that would have saved me from having to prepare a migration pat= h, but better late that never :) regards, Bapt --H+4ONPRPur6+Ovig Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlHdvEMACgkQ8kTtMUmk6EwdhgCfepn3ygB5bNxzzlF1CwJPndbS 7V8AoKKkJGGdXPGnwT0sjFUUBL15klG+ =Ms7X -----END PGP SIGNATURE----- --H+4ONPRPur6+Ovig--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130710195547.GB68830>