From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: Preliminary 'wip-armhf' branch pushed
Date: Wed, 31 Dec 2014 12:31:03 -0500 [thread overview]
Message-ID: <87lhln7mlk.fsf@netris.org> (raw)
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
next reply other threads:[~2014-12-31 17:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 17:31 Mark H Weaver [this message]
2014-12-31 17:47 ` Preliminary 'wip-armhf' branch pushed John Darrington
2014-12-31 19:23 ` Mark H Weaver
2014-12-31 20:20 ` John Darrington
2014-12-31 23:40 ` Mark H Weaver
2015-01-01 6:14 ` John Darrington
2015-01-01 7:11 ` Mark H Weaver
2015-01-01 7:24 ` John Darrington
2015-01-01 18:22 ` Mark H Weaver
2015-01-01 19:04 ` John Darrington
2015-01-02 20:48 ` Ludovic Courtès
2015-01-02 22:07 ` Mark H Weaver
2015-01-03 19:07 ` Ludovic Courtès
2014-12-31 22:24 ` Mark H Weaver
2014-12-31 22:55 ` Mark H Weaver
2015-01-01 18:53 ` Problem with natively-built armhf bootstrap compiler Mark H Weaver
2015-01-02 2:19 ` Mark H Weaver
2015-01-02 4:56 ` Mark H Weaver
2015-01-02 21:06 ` Ludovic Courtès
2015-01-03 18:37 ` Mark H Weaver
2015-01-07 13:15 ` Ludovic Courtès
2015-01-07 15:15 ` Mark H Weaver
2015-01-07 15:30 ` [PATCH] gnu: gcc-static: Remove -lgcc_s from GNU_USER_TARGET_LIB_SPEC Mark H Weaver
2015-01-07 17:15 ` Ludovic Courtès
2015-01-02 20:45 ` Preliminary 'wip-armhf' branch pushed Ludovic Courtès
2015-01-03 18:49 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhln7mlk.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).