From owner-freebsd-arch@FreeBSD.ORG Wed Jul 10 20:59:42 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 52000EF5; Wed, 10 Jul 2013 20:59:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2E6A21B86; Wed, 10 Jul 2013 20:59:42 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2A9CFB98A; Wed, 10 Jul 2013 16:59:41 -0400 (EDT) From: John Baldwin To: freebsd-arch@freebsd.org Subject: Re: Adding a MACHINE_ARCH note Date: Wed, 10 Jul 2013 16:11:37 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <32F979BD-FB5C-4111-9586-4C5E7C6DFA71@bsdimp.com> <20130710195547.GB68830@ithaqua.etoilebsd.net> In-Reply-To: <20130710195547.GB68830@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201307101611.37437.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 10 Jul 2013 16:59:41 -0400 (EDT) Cc: Baptiste Daroussin , Dimitry Andric , Adrian Chadd , Andrew Turner 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 20:59:42 -0000 On Wednesday, July 10, 2013 3:55:47 pm Baptiste Daroussin wrote: > On Wed, Jul 10, 2013 at 12:26:42PM -0700, Adrian Chadd wrote: > > On 10 July 2013 09:55, Warner Losh wrote: > > > > >> 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. > > > > Sweet. > > > > Thanks! > > > > > > -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 support. > > pkgng needs for example to allow i386 packages to be installed on amd64 because > 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. You should look at how MACHINE_CPUARCH vs MACHINE vs MACHINE_ARCH works. Keep in mind that amd64/i386/pc98 should probably have MACHINE_CPUARCH of x86, but we just haven't done that yet. If we did that I think you could follow src's conventions and be fine. Something like: os:version:cpuarch:arch Where cpuarch == MACHINE_CPUARCH (should be x86 on amd64/i386/pc98, but isn't yet. It ss sane on other platforms) and arch == MACHINE_ARCH (amd64/i386 (for pc98 MACHINE_ARCH is i386)) So that would give: freebsd:9:x86:amd64 freebsd:9:x86:i386 (for both pc98 and i386) freebsd:9:arm:armv6 etc. I think that means we could eventually support x32 as: freebsd:9:x86:x32 We might have an x32 world (but perhaps not a kernel?, though we would need the headers to DTRT) -- John Baldwin