Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Sep 2013 07:49:07 +0200
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        Nathan Whitehorn <nwhitehorn@freebsd.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org
Subject:   Re: svn commit: r255457 - head/usr.sbin/pkg
Message-ID:  <20130911054907.GK40186@ithaqua.etoilebsd.net>
In-Reply-To: <522FE3A2.2090405@freebsd.org>
References:  <201309102056.r8AKu1rQ000442@svn.freebsd.org> <522FE3A2.2090405@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--bPg9NdpM9EETxvqt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 10, 2013 at 10:29:38PM -0500, Nathan Whitehorn wrote:
> On 09/10/13 15:56, Baptiste Daroussin wrote:
> > Author: bapt
> > Date: Tue Sep 10 20:56:01 2013
> > New Revision: 255457
> > URL: http://svnweb.freebsd.org/changeset/base/255457
> >
> > Log:
> >    Add support to detect arm vs armv6
> >   =20
> >    There are two different versions of the ARM ABI depending on the
> >    TARGET_ARCH. As these are sligntly different a package built for
> >    one may not work on another. We need to detect which one we are on
> >    by parsing the .ARM.attributes section.
> >   =20
> >    This will only work on the ARM EABI as this section is part of the
> >    ABI definition. As armv6 only supports the ARM EABI this is not a
> >    problem for the oabi.
> >   =20
> >    Older versions of libelf in FreeBSD fail to read the
> >    .ARM.attributes section needed. As armv6 is unsupported on these
> >    versions we can assume we are running on arm.
> >   =20
>=20
> Picking a random commit: I don't suppose we can just use MACHINE_ARCH=20
> for these identifiers? It encapsulates everything needed for compatibilit=
y.
> -Nathan

Yes we probably can, it encapsulates everything since recently! It wasn't t=
he
case when ABI string was defined, and it lacks an important part of why the=
 ABI
string has been designed on pkgng: making a package match multiple arch via
simple glob on the ABI line.

So as I already said to Warner, Yes now that it properly works on all arche=
s we
could use it but that is not that easy.

People wanting to go that way should:
1. provide a way for pkgng to extract MARCHE_ARCH out of a binary (/bin/ls)
(dynamic cross installation ABI detection)
2. provide a way to create multiarch ABI out of MACHINE_ARCH
3. provide an upgrade path with compatibility for the current string (pkgng=
 is
already largely deployed)
4. have time to do it

There is so much work pending on pkgng, in particular for 10.0 that I just =
have
no time to work on it.

regards,
Bapt

--bPg9NdpM9EETxvqt
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlIwBFMACgkQ8kTtMUmk6EyDAACeNr0ekbof6H/uHYuzismf/iKr
W1kAniJ5z0SWLnLmRlZcniQ9lUwpY/dw
=CRDN
-----END PGP SIGNATURE-----

--bPg9NdpM9EETxvqt--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130911054907.GK40186>