From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: Pass --build=<triplet> to native builds by default?
Date: Sat, 03 Jan 2015 15:01:23 -0500 [thread overview]
Message-ID: <87egrby6p8.fsf@netris.org> (raw)
It turns out that on ARM systems, the result of 'config.guess' depends
on the result of 'uname -m'. In other words, details of the kernel (and
perhaps processor?) on the build machine will determine the triplet of
our builds, which in turn may affect what set of instructions is used.
Therefore, I think that on ARM systems (and perhaps _all_ systems), we
should consider passing --build=<triplet> to configure by default.
What do you think?
Mark
next reply other threads:[~2015-01-03 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 20:01 Mark H Weaver [this message]
2015-01-03 21:01 ` Pass --build=<triplet> to native builds by default? Ludovic Courtès
2015-01-03 22:11 ` Mark H Weaver
2015-01-03 22:15 ` Mark H Weaver
2015-01-04 16:20 ` Ludovic Courtès
2015-01-04 19:11 ` Mark H Weaver
2015-01-04 20:18 ` Ludovic Courtès
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=87egrby6p8.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).