unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 7/9] gnu: idris: Update to 0.12.3.
Date: Sat, 3 Dec 2016 16:06:14 -0500	[thread overview]
Message-ID: <20161203210614.GB22684@jasmine> (raw)
In-Reply-To: <CAL1_imn_8=wU3jBsRs_0qLhsQz_qgHuE3Nfno_Kvhp5Ui430tA@mail.gmail.com>

On Sat, Dec 03, 2016 at 09:26:02PM +0100, David Craven wrote:
> > Why do we need to skip the tests?
> 
> First idris is not found, then after adding dist/build/idris to PATH,
> the idris libraries aren't found. So I set IDRIS_LIBRARY_PATH to libs.
> Then the idris runtime system isn't found, so I added rts to
> C_INCLUDE_PATH and LIBRARY_PATH. Half of the tests still fail with
> blah not found. I think that runhaskell Setup.hs test doesn't set the
> working directory correctly. I spent some time trying to track down
> the issue further, but couldn't figure out how to build a Haskell
> project locally:
> 
> guix environment idris
> ghc-pkg --package-db=package.conf.d recache
> GHC_PACKAGE_PATH= runhaskell Setup.hs configure --package-db=package.conf.d
> 
> That's the point when I gave up. If someone knows how I can build a
> Haskell project without too much hassle. IDRIS_LIBRARY_PATH currently
> only takes one path. To package idris libraries it would be nice to
> extend IDRIS_LIBRARY_PATH to a colon separated list, but without a
> simple way to build the project (incrementally) it looks like too much
> of a hassle...

Okay, I think you should summarize this in a code comment :)

  reply	other threads:[~2016-12-03 21:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03 10:42 [PATCH 1/9] gnu: Add ghc-hinotify David Craven
2016-12-03 10:42 ` [PATCH 2/9] gnu: Add ghc-fsnotify David Craven
2016-12-03 19:59   ` Leo Famulari
2016-12-03 10:42 ` [PATCH 3/9] gnu: Add ghc-tasty-rerun David Craven
2016-12-03 20:00   ` Leo Famulari
2016-12-03 10:42 ` [PATCH 4/9] gnu: Add ghc-ieee754 David Craven
2016-12-03 20:01   ` Leo Famulari
2016-12-10 10:15     ` David Craven
2016-12-03 10:42 ` [PATCH 5/9] gnu: Add ghc-terminal-size David Craven
2016-12-03 20:01   ` Leo Famulari
2016-12-03 10:42 ` [PATCH 6/9] gnu: ghc-trifecta: Update to 1.6 David Craven
2016-12-03 20:02   ` Leo Famulari
2016-12-03 10:42 ` [PATCH 7/9] gnu: idris: Update to 0.12.3 David Craven
2016-12-03 20:03   ` Leo Famulari
2016-12-03 20:26     ` David Craven
2016-12-03 21:06       ` Leo Famulari [this message]
2016-12-03 10:42 ` [PATCH 8/9] gnu: coq: Update to 8.5pl2 David Craven
2016-12-03 20:09   ` Leo Famulari
2016-12-03 10:42 ` [PATCH 9/9] gnu: Add ocaml-menhir David Craven
2016-12-03 19:56   ` Leo Famulari
2016-12-03 20:12   ` Leo Famulari
2016-12-03 19:58 ` [PATCH 1/9] gnu: Add ghc-hinotify Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161203210614.GB22684@jasmine \
    --to=leo@famulari.name \
    --cc=david@craven.ch \
    --cc=guix-devel@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).