From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Darrington Subject: Re: Preliminary 'wip-armhf' branch pushed Date: Wed, 31 Dec 2014 18:47:19 +0100 Message-ID: <20141231174719.GA8456@intra> References: <87lhln7mlk.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49916) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y6NMm-0006T7-7u for guix-devel@gnu.org; Wed, 31 Dec 2014 12:47:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y6NMh-0007BQ-Pp for guix-devel@gnu.org; Wed, 31 Dec 2014 12:47:28 -0500 Received: from de.cellform.com ([88.217.224.109]:55894 helo=jocasta.intra) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y6NMh-0007BE-BP for guix-devel@gnu.org; Wed, 31 Dec 2014 12:47:23 -0500 Content-Disposition: inline In-Reply-To: <87lhln7mlk.fsf@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Mark H Weaver Cc: guix-devel@gnu.org --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It would seem then, that the only difference between the wip-arm and the wi= p-armhf branches is the value of the --with-fpu flag. I'm not an ARM expert, so I don't know how important that setting is. But = I do know that there are many different fpus - if we are going to have a new branch f= or every combination of flags then there are going to be rather a lot of branches. We need to find a better solution. J' On Wed, Dec 31, 2014 at 12:31:03PM -0500, Mark H Weaver wrote: Hello Guix, =20 I've pushed a new branch 'wip-armhf' (not to be confused with 'wip-arm= ') which seems likely to finish natively building bootstrap tarballs soon. It is based on the 'core-updates' branch. =20 I chose system name "armhf-linux", GNU triplet "arm-linux-gnueabihf", and the following GCC configure flags: =20 --with-arch=3Darmv7-a --with-float=3Dhard --with-mode=3Dthumb --with-fpu=3Dvfpv3-d16 =20 I believe this coincides with what Debian does for their 'armhf' port. =20 This branch is *not* ready for use. For one thing, the current bootstrap tarballs are cross-compiled, and we should wait for the natively-compiled ones. =20 The branch is for review. Comments and suggestions solicited! =20 Mark --=20 PGP Public key ID: 1024D/2DE827B3=20 fingerprint =3D 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSkNqUACgkQimdxnC3oJ7MicwCfZrXUcDWP/V+zKyB7IyI/l9e/ qaQAn3bknTj7qqx1vLtEHGsSGtfXFJbp =PAaf -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--