From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add Jellyfish.
Date: Fri, 01 Jan 2016 23:15:12 +0100 [thread overview]
Message-ID: <87ziwpdk0f.fsf@gnu.org> (raw)
In-Reply-To: <idj7fjwhqrg.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Wed, 30 Dec 2015 16:58:59 +0100")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ben Woodcroft <b.woodcroft@uq.edu.au> skribis:
>>
>>> But would it be possible to include the scripting language bindings,
>>> something along these lines?
>>>
>>> + (arguments
>>> + `(#:configure-flags '("--enable-ruby-binding"
>>> + "--enable-python-binding"
>>> + "--enable-perl-binding")
>>
>> There’s the usual space/popularity tradeoff to take into account: adding
>> them all makes the package’s closure much larger, so it’s important to
>> add only the useful bindings by default.
>>
>> Ideally, the .so for these bindings could be moved to separate outputs
>> (like we did for the “tk” output of Python), but it’s not always easy to
>> do.
>
> In this case it seems to be very easy to separate the bindings into
> different outputs as the flags take an optional path.
Great.
> However, the test for the Perl bindings does not pass:
>
> /gnu/store/czs63sm4l0s4a56ab38dqvkx19yzylbq-perl-5.16.1/bin/perl: symbol lookup error: /tmp/nix-build-jellyfish-2.2.4.drv-0/jellyfish-2.2.4/.libs/libjellyfish-2.0.so.2: undefined symbol: pthread_create
> FAIL tests/swig_perl.sh (exit status: 127)
>
> Maybe the library needs another linker flag? I’ll play with this later
> and see if I can make it work. If not I’ll leave the Perl bindings (and
> the “perl” output) away for now.
Looks like libjellyfish-2.0.so lacks “-pthread” in its LDFLAGS. Perl
dlopening reveals the problem, it seems.
> It’s a bit unfortunate that this library would gain so many transitive
> inputs just for these bindings (all of these three languages require a
> lot of inputs). It would be nice if we could somehow mark certain
> inputs to be used only for certain outputs, but that’s probably a silly
> wish.
At least someone using substitutes won’t need to download all these
prerequisites if bindings are moved to individual outputs.
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-01-01 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 16:42 [PATCH] Add Jellyfish Ricardo Wurmus
2015-12-18 18:19 ` Eric Bavier
2015-12-18 23:25 ` Ben Woodcroft
2015-12-20 22:43 ` Ludovic Courtès
2015-12-30 15:58 ` Ricardo Wurmus
2016-01-01 22:15 ` Ludovic Courtès [this message]
2016-01-06 11:13 ` Ricardo Wurmus
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=87ziwpdk0f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.