From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: Mark H Weaver <mhw@netris.org>
Cc: 29516@debbugs.gnu.org
Subject: bug#29516: Maxima fails to build
Date: Sun, 03 Dec 2017 15:58:38 +0100 [thread overview]
Message-ID: <87wp23oo2p.fsf@GlaDOS.home> (raw)
In-Reply-To: <874lp912or.fsf@netris.org> (Mark H. Weaver's message of "Sat, 02 Dec 2017 12:04:36 -0500")
Mark H Weaver <mhw@netris.org> writes:
> Diego Nicola Barbato <dnbarbato@posteo.de> writes:
>
>> Leo Famulari <leo@famulari.name> writes:
>>
>>> On Fri, Dec 01, 2017 at 11:53:01AM +0100, Diego Nicola Barbato wrote:
>>>> `guix build maxima' fails during the `check' phase with the following
>>>> output:
>>>
>>> Thanks for your report!
>
> FYI, the Maxima builds started failing after the recent upgrade to
> 'gcl'. I raised the issue here:
>
> https://lists.gnu.org/archive/html/guix-devel/2017-11/msg00341.html
>
> The person who upgraded 'gcl' first said that he could reproduce the
> build failure locally, and then said that he couldn't. I'm not sure
> what happened there.
>
> Mark
This seems to be quite a strange issue indeed: Out of curiosity I tried
the same thing in a VM (guix system vm-image) and even though it is the
same architecture (x86_64) and the same commit
(e2721a05e7d778bdf845b7cb7a42fd9f76095b69) guix consistently succeeds to
build maxima in the VM while it consistently fails to build on my
laptop. I also tried building with only one core on my laptop and
running the VM with two cores (qemu-system-x86_64 -smp cores=2) with the
same result. `guix build maxima' only fails on the VM when I run it
with `--rounds=2' because the outputs differ.
Diego
next prev parent reply other threads:[~2017-12-03 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 10:53 bug#29516: Maxima fails to build Diego Nicola Barbato
2017-12-01 17:45 ` Leo Famulari
2017-12-01 21:13 ` Diego Nicola Barbato
2017-12-02 17:04 ` Mark H Weaver
2017-12-03 14:58 ` Diego Nicola Barbato [this message]
2019-02-15 9:03 ` Diego Nicola Barbato
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=87wp23oo2p.fsf@GlaDOS.home \
--to=dnbarbato@posteo.de \
--cc=29516@debbugs.gnu.org \
--cc=mhw@netris.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.