[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Preliminary 'wip-armhf' branch pushed
From: |
John Darrington |
Subject: |
Re: Preliminary 'wip-armhf' branch pushed |
Date: |
Wed, 31 Dec 2014 18:47:19 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
It would seem then, that the only difference between the wip-arm and the
wip-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 for
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,
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.
I chose system name "armhf-linux", GNU triplet "arm-linux-gnueabihf",
and the following GCC configure flags:
--with-arch=armv7-a
--with-float=hard
--with-mode=thumb
--with-fpu=vfpv3-d16
I believe this coincides with what Debian does for their 'armhf' port.
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.
The branch is for review. Comments and suggestions solicited!
Mark
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
signature.asc
Description: Digital signature