From: Andy Wingo <wingo@pobox.com>
To: guile-user@gnu.org
Subject: Re: C module problem
Date: Mon, 28 Feb 2011 22:37:28 +0100 [thread overview]
Message-ID: <m3fwr7rgbr.fsf@unquote.localdomain> (raw)
In-Reply-To: <20110228081326.GA25446@neko> (Aidan Gauland's message of "Mon, 28 Feb 2011 21:13:27 +1300")
Hi Aidan,
On Mon 28 Feb 2011 09:13, Aidan Gauland <aidalgol@no8wireless.co.nz> writes:
> I am trying to write a simple C module for Guile (for the learning
> experience) and I have run into a cryptic error.
Apologies for this. It is actually a libltdl issue:
"As I am sure many are aware, libltdl's error reporting is pretty
dumb, lt_dlerror() regularly reports things like "file not found"
where the actual problem might be something completely different, and
a reasonable error string may be readily available from dlerror()."
http://lists.gnu.org/archive/html/libtool/2010-06/msg00056.html
> gcc -shared -o sdl-guile.so -fPIC sdl-guile.c `guile-config compile` `sdl-config --cflags`
In this case loading the library fails probably because you did not add
SDL libs. `sdl-config --cflags --libs` perhaps? Just a guess.
That said, the dynamic FFI is more fun; and also, there is a guile-sdl
package out there somewhere.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-28 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 8:13 C module problem Aidan Gauland
2011-02-28 8:54 ` nalaginrut
2011-02-28 9:32 ` Aidan Gauland
2011-02-28 21:37 ` Andy Wingo [this message]
2011-02-28 23:23 ` Aidan Gauland
-- strict thread matches above, loose matches on Subject: below --
2011-02-28 9:40 nalaginrut
2011-02-28 10:16 ` rm
2011-02-28 14:54 Mike Gran
2011-02-28 15:35 ` gustav
2011-02-28 17:30 ` dsmich
2011-02-28 18:24 ` Aidan Gauland
2011-02-28 20:43 ` Aidan Gauland
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=m3fwr7rgbr.fsf@unquote.localdomain \
--to=wingo@pobox.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).