From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add mash.
Date: Thu, 01 Sep 2016 11:00:39 +0100 [thread overview]
Message-ID: <87shtkq6rc.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87zinsae3u.fsf@elephly.net>
Leo Famulari <leo@famulari.name> writes:
>> + (add-after 'unpack 'fix-includes
>> + (lambda _
>> + (substitute* '("src/mash/Sketch.cpp" "src/mash/CommandFind.cpp")
>> + (("^#include \"kseq\\.h\"")
>> + "#include \"htslib/kseq.h\""))
>> + #t))
>> + (add-before 'configure 'autoconf
>> + (lambda _ (zero? (system* "autoconf")))))))
>> + (native-inputs
>> + `(("autoconf" ,autoconf)
>> + ("capnproto" ,capnproto)
>> + ("htslib" ,htslib)))
>
> Does it only need to use capnproto and htslib while building? Okay if
> so.
I had these in inputs initially and was surprised to see no references.
Both seems to be compiled into the final program[0]: when running "mash
info" on an invalid file (the provided data/refseq.msh), a generic
capnproto exception is thrown (src/capnp/serialize.c++:159).
That raises another question: should the htslib and capnproto licenses
be listed too, since they are part of the binary output?
I'm not a bioinformatician (just a mere sysadmin for such), but have
been going through the tutorial and things appear to work fine.
0: https://github.com/marbl/Mash/blob/master/Makefile.in#L38
next prev parent reply other threads:[~2016-09-01 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 17:54 [PATCH] gnu: Add mash Marius Bakke
2016-08-31 19:44 ` Leo Famulari
2016-08-31 20:16 ` Ricardo Wurmus
2016-09-01 10:00 ` Marius Bakke [this message]
2016-09-06 21:01 ` Leo Famulari
2016-09-08 22:06 ` Marius Bakke
2016-09-10 21:20 ` Leo Famulari
2016-09-10 21:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shtkq6rc.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--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.