[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 01/01: gnu: python-setuptools: Update to 12.1.
From: |
Mark H Weaver |
Subject: |
Re: 01/01: gnu: python-setuptools: Update to 12.1. |
Date: |
Wed, 18 Feb 2015 14:59:24 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
Andreas Enge <address@hidden> 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