From owner-freebsd-arch@FreeBSD.ORG Wed Jul 10 19:55:53 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 752556C5; Wed, 10 Jul 2013 19:55:53 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id ABE421892; Wed, 10 Jul 2013 19:55:52 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id l18so6196817wgh.2 for ; Wed, 10 Jul 2013 12:55:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=1yKmgUFE/5BRuz7IGpAy9M2QOY0vl6X/0h7diPjPLvU=; b=S1MPvuIR0GJR3xJEb/KIFhOOna0878iO7i0ZXyzqoe/532NmoAHMyWm7RMzsNNndJ3 0L8iQ+jBxcadb03KEOPLgPjVIzYM1oWDk7N7AkYlkpaupYSVV1s/62m/TAoNXE23opsm CE4NNPYpAcaGA2j88bjU97z4fSqc67ByzCwzl8qO64Y6gPLte9mYVK3dqOzDj1JfuAjT EApoXWLgR8QvBPaBgcREnN7ettHRX9ayQQEWhNqmnlYy+VH5Pq4eVGl9qJLWEjSwwxyx vmvotvBnMbmpj6UySOwF90QAaZi12dznRpQ+3yjl+YRpOrJ6rdvzPhehU337KOUyg8NI 9A4Q== X-Received: by 10.195.12.202 with SMTP id es10mr19359293wjd.17.1373486151695; Wed, 10 Jul 2013 12:55:51 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id em10sm60045535wid.1.2013.07.10.12.55.50 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 10 Jul 2013 12:55:50 -0700 (PDT) Sender: Baptiste Daroussin Date: Wed, 10 Jul 2013 21:55:47 +0200 From: Baptiste Daroussin To: Adrian Chadd Subject: Re: Adding a MACHINE_ARCH note Message-ID: <20130710195547.GB68830@ithaqua.etoilebsd.net> References: <32F979BD-FB5C-4111-9586-4C5E7C6DFA71@bsdimp.com> <20130709234837.559e3769@bender.Home> <752588A3-C0EF-4844-A0EE-4657CAD40E4C@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H+4ONPRPur6+Ovig" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dimitry Andric , Andrew Turner , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 19:55:53 -0000 --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 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--