From: Marius Bakke <mbakke@fastmail.com>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH 2/3] gnu: Add python-pyxb.
Date: Sat, 24 Sep 2016 04:15:00 +0100 [thread overview]
Message-ID: <87vaxmxa2z.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <4cc91e33-1722-91e7-eda3-38b967fc1e73@uq.edu.au>
Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
>> Htslib is propagated because it
>> is included by the installed samtools and bcftools headers; at least one
>> of pysams dependencies failed to build when it was a regular input.
> Ah, I see. Can this be avoided with patchelf?
I don't think so. The htslib headers need to be propagated for anything
that uses header files from pysam, since they contain contain code such
as "include <htslib/foo.h>". Perhaps you can update the comment to make
it more clear?
Patchelf is probably what made that work when htslib was bundled.
Cheers,
Marius
next prev parent reply other threads:[~2016-09-24 3:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 10:10 [PATCH 0/3] gnu: python2-pbcore: Update to 1.2.10 Marius Bakke
2016-09-17 10:10 ` [PATCH 1/3] gnu: python-pysam: Update to 0.9.1.4 Marius Bakke
2016-09-17 10:10 ` [PATCH 2/3] gnu: Add python-pyxb Marius Bakke
[not found] ` <3bd16b58-b3d1-d47c-2433-c3a721681463@uq.edu.au>
2016-09-20 6:34 ` Ben Woodcroft
2016-09-20 7:06 ` Ben Woodcroft
2016-09-21 21:14 ` Marius Bakke
2016-09-22 0:46 ` Ben Woodcroft
2016-09-22 15:15 ` Marius Bakke
2016-09-23 1:28 ` Ben Woodcroft
2016-09-23 15:56 ` Marius Bakke
2016-09-23 16:06 ` Marius Bakke
2016-09-24 0:23 ` Ben Woodcroft
2016-09-24 3:15 ` Marius Bakke [this message]
2016-09-26 11:15 ` Ben Woodcroft
2016-09-26 18:32 ` Marius Bakke
2016-09-27 11:01 ` Ben Woodcroft
2016-09-30 20:12 ` Ludovic Courtès
2016-09-17 10:10 ` [PATCH 3/3] gnu: python2-pbcore: Update to 1.2.10 Marius Bakke
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=87vaxmxa2z.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=b.woodcroft@uq.edu.au \
--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 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.