From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Guile Build Errors
Date: Wed, 02 Sep 2009 13:49:12 +0200 [thread overview]
Message-ID: <8763c1zhvr.fsf@gnu.org> (raw)
In-Reply-To: 25254370.post@talk.nabble.com
Hi,
bornlibra23 <awarikoo@nse.co.in> writes:
>> That means `load-extension' et al. won't work (we could use Libtool's
>> preopen magic to make it work with static libraries, but we currently
>> don't).
> Can you tell me which of the tests are expected to fail?
Sometimes modules load extensions with `load-extension', e.g., the
`(srfi srfi-1)' module. On systems supporting shared libs, this
corresponds to a dlopen(3) call, which just won't work when building
static libraries, as is the case on your system.
GNU Libtool's `-dlpreopen' can be used so that `lt_dlopen_ext ()' can
actually do the right thing even when not building shared libraries.
Guile doesn't currently use it, but the sketch of a solution is at:
http://thread.gmane.org/gmane.lisp.guile.devel/7897 .
Would you like to try this out?
>> I guess your linker supports shared libs but the `configure' somehow fails
>> to see it. Apparently Libtool's `_LT_LINKER_SHLIBS' M4 macro hasn't been
>> ported to your platform, leading to this incorrect diagnostic. Can you
>> report this to bug-libtool@gnu.org?
> The system doesnt support shared libraries at all.
Oh, it really doesn't? Then indeed, you'd need the `dlpreopen' trick
above.
Note that you can already use (or rather debug ;-)) Guile without
`dlpreopen'. You just won't be able to load modules that call
`load-extension'. In 1.8, it means you cannot use SRFI-1 and SRFI-60.
>> Hmm, this looks fishy as `string-ci<?' is a primitive procedure defined in
>> libguile.
> Can you suggest something?
I don't have any clue right now. I'd first look at the "freed cell"
issue, which means that the GC probably fails to scan part of the stack.
Hope this helps,
Ludo'.
next prev parent reply other threads:[~2009-09-02 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 8:19 Guile Build Errors bornlibra23
2009-08-31 12:38 ` Ludovic Courtès
2009-09-01 8:30 ` bornlibra23
2009-09-02 8:44 ` Ludovic Courtès
2009-09-02 9:29 ` bornlibra23
2009-09-02 11:49 ` Ludovic Courtès [this message]
2009-10-04 22:25 ` Neil Jerram
2009-10-05 9:02 ` 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=8763c1zhvr.fsf@gnu.org \
--to=ludo@gnu.org \
--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).