From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: graphviz: Enable Guile library.
Date: Tue, 10 May 2016 15:31:38 +0200 [thread overview]
Message-ID: <87r3daghtx.fsf@gnu.org> (raw)
In-Reply-To: <8737pq8e9j.fsf@gnu.org> (Roel Janssen's message of "Tue, 10 May 2016 11:15:52 +0200")
Roel Janssen <roel@gnu.org> skribis:
> What is the preferred way to include the module file to the package?
> Should I create another package with this file alone, and use it as a
> propagated input for graphviz?
Could you first submit it upstream?
> I now have a graphviz-guile package with a graphviz.scm module file.
>
> Where should I link/copy/move libgv_guile.so?
>
> I tried:
> $PACKAGE_OUTPUT/lib/
> $PACKAGE_OUTPUT/lib/guile/2.0/
> $PACKAGE_OUTPUT/lib/guile/2.0/extensions/
>
> But it seems my system only looks in:
> /lib
> /gnu/store/...-gcc-4.9.3-lib/lib/
> /gnu/store/...-glibc-2.22/lib/
> /gnu/store/...-guile-2.0.11/lib/
‘load-extension’ searches for shared objects in the extension directory:
--8<---------------cut here---------------start------------->8---
scheme@(guix gexp)> (assoc-ref %guile-build-info 'extensiondir)
$14 = "/home/ludo/soft/lib/guile/2.0/extensions"
--8<---------------cut here---------------end--------------->8---
… and in whatever ‘LTDL_LIBRARY_PATH’ points to
(info "(libtool) Libltdl interface").
HTH!
Ludo’.
next prev parent reply other threads:[~2016-05-10 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 10:17 [PATCH] gnu: graphviz: Enable Guile library Roel Janssen
2016-05-09 20:37 ` Ludovic Courtès
2016-05-09 20:54 ` Roel Janssen
2016-05-10 5:53 ` Danny Milosavljevic
2016-05-10 9:15 ` Roel Janssen
2016-05-10 13:08 ` Roel Janssen
2016-05-10 13:31 ` Ludovic Courtès [this message]
2016-05-10 14:07 ` Roel Janssen
2016-05-11 14:04 ` Ludovic Courtès
2016-05-11 14:48 ` Roel Janssen
2016-05-11 16:22 ` Ludovic Courtès
2016-05-11 21:55 ` Roel Janssen
2016-05-17 20:48 ` Ludovic Courtès
2016-05-17 21:31 ` Roel Janssen
2016-05-19 12:08 ` Ludovic Courtès
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=87r3daghtx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=roel@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.