all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kei Kebreau <kkebreau@posteo.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: gcl: Update snapshot.
Date: Sun, 26 Nov 2017 13:07:58 -0500	[thread overview]
Message-ID: <87efokj4ld.fsf@posteo.net> (raw)
In-Reply-To: <87k1ydioru.fsf@posteo.net> (Kei Kebreau's message of "Sun, 26 Nov 2017 00:37:25 -0500")

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

Kei Kebreau <kkebreau@posteo.net> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> kkebreau@posteo.net (Kei Kebreau) writes:
>>
>>> kkebreau pushed a commit to branch master
>>> in repository guix.
>>>
>>> commit dd0134fcb707452e1c343d66af6088c0be38a285
>>> Author: Kei Kebreau <kkebreau@posteo.net>
>>> Date:   Wed Nov 22 13:47:33 2017 -0500
>>>
>>>     gnu: gcl: Update snapshot.
>>>     
>>>     * gnu/packages/lisp.scm (gcl): Update to 2.6.12-1.5956140.
>>>     [arguments]: Remove CFLAGS from and add GCL_CC and CC to
>>> make-flags; adjust
>>>     pre-conf phase.
>>>     
>>>     This update includes small upstream bug fixes and optimizations.
>>
>> Thanks for this.  Unfortunately, Maxima's test suite started failing,
>> and I guess this is the most likely cause.
>>
>>   https://hydra.gnu.org/build/2361466
>>
>> Would you be willing to investigate?
>>
>>      Mark
>
> Yes, I'm currently reproducing the build failure locally. Thank you for
> the notification.

So it turns out that I cannot reproduce this failure locally. Is there a
way that I access the failed build tree?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-11-26 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171124195115.10912.95803@vcs0.savannah.gnu.org>
     [not found] ` <20171124195116.23ECF209D7@vcs0.savannah.gnu.org>
2017-11-26  3:40   ` 01/01: gnu: gcl: Update snapshot Mark H Weaver
2017-11-26  5:37     ` Kei Kebreau
2017-11-26 18:07       ` Kei Kebreau [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=87efokj4ld.fsf@posteo.net \
    --to=kkebreau@posteo.net \
    --cc=guix-devel@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.