l...@gnu.org (Ludovic Courtès) skribis:
> OK. Then we effectively need to proceed as you suggest: Build
> python-minimal (which does not depend on Tk), build Tk, and then build
> python.
Done in commits 95288fc and afa181f.
Thanks,
Ludo’.
l...@gnu.org (Ludovic Courtès) skribis:
> OK. Then we effectively need to proceed as you suggest: Build
> python-minimal (which does not depend on Tk), build Tk, and then build
> python.
Done in commits 95288fc and afa181f.
Thanks,
Ludo’.
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver skribis:
>>
>>> l...@gnu.org (Ludovic Courtès) writes:
>>>
t...@gmplib.org (Torbjörn Granlund) skribis:
> This is most surely a hardware problem. The most common such problem is
> a bad RAM chip
l...@gnu.org (Ludovic Courtès) writes:
OK, I’ll see if I can reproduce it on another ARMv7 machine and
report back.
Good. Incidentally, we run nightly builds on a bunch of ARMv7 machines.
However, the machine in question is a build machine and it would be
surprising for the RAM issue
Andreas Enge writes:
> On Wed, Oct 07, 2015 at 08:45:09AM -0400, Mark H Weaver wrote:
>> When used as a build slave, the Novena is prone to overheating. The
>> best solution is to add a fan. In the meantime, I've disabled 2 out of
>> the 4 cores on hydra-slave1 using the following commands:
>
>
On Wed, Oct 07, 2015 at 08:45:09AM -0400, Mark H Weaver wrote:
> When used as a build slave, the Novena is prone to overheating. The
> best solution is to add a fan. In the meantime, I've disabled 2 out of
> the 4 cores on hydra-slave1 using the following commands:
Which temperature is overheati
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>>
>>> t...@gmplib.org (Torbjörn Granlund) skribis:
>>>
This is most surely a hardware problem. The most common such problem is
a bad RAM chip.
>>>
>>> OK, I’ll see if I can repr
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> t...@gmplib.org (Torbjörn Granlund) skribis:
>>
>>> This is most surely a hardware problem. The most common such problem is
>>> a bad RAM chip.
>>
>> OK, I’ll see if I can reproduce it on another ARMv7 machine and
>> report bac
