unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Roland Orre <roland.orre@gmail.com>
To: Alexei Matveev <alexei.matveev@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Sabotage against guile users?
Date: Wed, 10 Jul 2013 23:12:35 +0200	[thread overview]
Message-ID: <CA+Sr8wWJgqFQnFjvSdCd2q5BqRA0wQwqZBt5c6dEWXLnV1rwfA@mail.gmail.com> (raw)
In-Reply-To: <CACMrLAfLnAWgQxqFJqSCQ2odr9Jnvy_fWJmcupwpBoyMczf6nA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]

Hi Alexi,
thanks for your reply.
The builds works fine, but when loading the module, e.g.
(use-modules (bcpnn2))
which contains
(load-extension (string-append bcpnn2-path ".libs/libbcpnn"
"scm_init_bcpnn")
I get the error message
./bcpnn2.scm:13:1: In procedure dynamic-link in expression (load-extension
(string-append bcpnn2-path ".libs/libbcpnn") "scm_init_bcpnn"):
./bcpnn2.scm:13:1: file: "/home/orre/work/guile/bcpnn-2.1/.libs/libbcpnn",
message: "file not found"
despite that directory contains a lot of recently built files like
bcpnn.o bits.o libbcpnn.a libbcpnn.la libbcpnn.lai libbcpnn.so
libbcpnn.so.0 mymath.o sets.o time.o user.o
However, I see that on a machine where this still works with guile-1.8.5 I
actually call a  bash script which sets LD_LIBRARY_PATH and
LTDL_LIBRARY_PATH as well
but the latter only for readline and LD_LIBRARY_PATH only points to guile's
libltdl/lib and guile/lib but I haven't checked if these are still
necessary.

The main problem is that I've never seen any kind of documentation upon how
doing this correct, my only documentation has been e.g
examples/box-dynamic-module/Makefile
which I've utilized and modified, but that no longer exists.

I would be very glad to be hinted about where I can actually find the
correct and precise doc for making dynamically loadable modules, which is
fundamental for anything I do.
Apart from that I really love guile. I even used the precursor to guile,
Aubrey Jaffer's scm before guile, in a similar manner, but at that time I
had to statically link scm  with my extensions.

On Wed, Jul 10, 2013 at 7:49 PM, Alexei Matveev <alexei.matveev@gmail.com>wrote:

>
> Hi, Roland,
>
> What exactly goes wrong when you build your module?
> Did you accidentally the error message?
>
> I use this convenience command to augment the linker and compiler flags:
>
>         LIBS += $(shell guile-config link)
>         INCDIRS += $(shell guile-config compile)
>
> Alexei
>

[-- Attachment #2: Type: text/html, Size: 2512 bytes --]

  reply	other threads:[~2013-07-10 21:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 13:11 Sabotage against guile users? Roland Orre
2013-07-10 13:25 ` Roland Orre
2013-07-10 17:49   ` Alexei Matveev
2013-07-10 21:12     ` Roland Orre [this message]
2013-07-10 22:15       ` Ludovic Courtès
2013-07-12  9:04       ` Thien-Thi Nguyen
2013-07-10 22:10 ` Ludovic Courtès
2013-07-10 23:52   ` Roland Orre
2013-07-11  0:24     ` Roland Orre
2013-07-11 11:47       ` Ludovic Courtès
2013-07-11 11:43     ` 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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=CA+Sr8wWJgqFQnFjvSdCd2q5BqRA0wQwqZBt5c6dEWXLnV1rwfA@mail.gmail.com \
    --to=roland.orre@gmail.com \
    --cc=alexei.matveev@gmail.com \
    --cc=guile-user@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.
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).