From: Robert Vollmert <rob@vllmrt.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: haskell changes
Date: Fri, 16 Aug 2019 20:14:24 +0200 [thread overview]
Message-ID: <FD35CD99-0315-49CD-88D1-42488DD3121A@vllmrt.net> (raw)
In-Reply-To: <87pnl556hw.fsf@elephly.net>
Hi Ricardo,
> On 16. Aug 2019, at 20:07, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> I have some Haskell-related changes ready for review and ideally merge
>> on wip-haskell-updates.
>>
>> I’ve tested them locally to the extent I managed; is CI broken or did I break
>> something there? http://ci.guix.gnu.org/jobset/wip-haskell-updates
>
> These errors usually mean that Cuirass didn’t even get to compute the
> evaluation. Have you tried compiling your branch locally to see if
> perhaps there’s an obstacle to compiling Guix?
thanks for the pointer, I will try a clean build now. I did build locally in
the sense of calling “make”, but it’s possible that I missed some missing
imports — I sometimes get warnings about unresolved variable names that
don’t cause the build to fail, though trying to `guix build` the corresponding
package later does fail.
Is there some `guix build` invocation I could call to build whatever `guix pull`
would build? I imagine that might be where cuirass is failing now?
While running the clean make, I got the following warnings I remember seeing
before — might these be the root of the problem? In that case I’ll see if I’m
too far behind master.
[ 11%] LOAD guix/scripts/archive.scm
WARNING: (guix scripts archive): `error-source' imported from both (gcrypt common) and (gcrypt pk-crypto)
WARNING: (guix scripts archive): `error-string' imported from both (gcrypt common) and (gcrypt pk-crypto)
Cheers
Robert
next prev parent reply other threads:[~2019-08-16 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 17:57 haskell changes Robert Vollmert
2019-08-16 18:07 ` Ricardo Wurmus
2019-08-16 18:14 ` Robert Vollmert [this message]
2019-08-16 20:16 ` Timothy Sample
2019-08-19 1:09 ` Timothy Sample
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=FD35CD99-0315-49CD-88D1-42488DD3121A@vllmrt.net \
--to=rob@vllmrt.net \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.