From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: python-setuptools: Update to 12.1.
Date: Wed, 18 Feb 2015 14:59:24 -0500 [thread overview]
Message-ID: <871tln6ler.fsf@netris.org> (raw)
In-Reply-To: <20150218083346.GA29709@debian.math.u-bordeaux1.fr> (Andreas Enge's message of "Wed, 18 Feb 2015 09:33:46 +0100")
Andreas Enge <andreas@enge.fr> writes:
> On Tue, Feb 17, 2015 at 10:46:11PM -0500, Mark H Weaver wrote:
>> Strangely, this update broke python-urwid-1.3.0.x86_64-linux. Three
>> tests involving newlines broke:
>
> Even more strangely, it builds without problems on my machine.
>
> I wonder if something is wrong with the hydra build machine setup, or if
> we still have some kind of impurity in the build system.
The most notable impurity is the kernel. Also, on several platforms,
including ARM, config.guess looks at 'uname -m' to find out the specific
processor type in the build machine to decide what triplet to use.
That's why I advocated passing --build= to configure by default for all
builds here:
https://lists.gnu.org/archive/html/guix-devel/2015-01/msg00037.html
However, there was pushback and the discussion stalled.
Even if we pass --build= to bypass config.guess, some packages probe the
details of the build machine and/or kernel and specialize the build for
those.
In theory, we could perform all builds within a VM and include the VM
build+configuration and kernel in the hash computation, but that would
obviously increase the resources needed to build things quite a lot.
Mark
prev parent reply other threads:[~2015-02-18 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150215221146.8024.17763@vcs.savannah.gnu.org>
[not found] ` <E1YN7Pm-00026R-OM@vcs.savannah.gnu.org>
2015-02-18 3:46 ` 01/01: gnu: python-setuptools: Update to 12.1 Mark H Weaver
2015-02-18 8:33 ` Andreas Enge
2015-02-18 8:57 ` Andreas Enge
2015-02-18 9:17 ` Andreas Enge
2015-02-18 19:59 ` Mark H Weaver [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tln6ler.fsf@netris.org \
--to=mhw@netris.org \
--cc=andreas@enge.fr \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.