unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Extension search path changed in 1.9
Date: Fri, 11 Feb 2011 16:33:41 +0100	[thread overview]
Message-ID: <m37hd6egbu.fsf@unquote.localdomain> (raw)
In-Reply-To: <87d3pv3gjr.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 23 Nov 2010 21:56:24 +0100")

Hi Ludovic,

On Tue 23 Nov 2010 21:56, ludo@gnu.org (Ludovic Courtès) writes:

> In 1.8, to run the test suite of libguile-foo from its build tree, I
> typically had a ‘pre-inst-guile’ like this:
>
> exec @abs_top_builddir@/libtool --mode=execute			\
>        -dlopen "@abs_top_builddir@/src/libguile-foo.la"	\
>        @GUILE@ "$@"
>
> which amounts to “LD_LIBRARY_PATH=$PWD/src/.libs:$LD_LIBRARY_PATH” on
> GNU/Linux.
>
> However, this no longer works with 2.0: if libguile-foo.so is already
> present in SCM_EXTENSIONS_DIR, then it will be loaded instead of the one
> from the build tree.

This sounds like a bad change.  Should we append to the
LTDL_LIBRARY_PATH environment variable instead?  I guess that's what we
need to do with the libtools that are "out there".

WDYT?

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-02-11 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 20:56 Extension search path changed in 1.9 Ludovic Courtès
2011-02-11 15:33 ` Andy Wingo [this message]
2011-02-11 16:01   ` Ludovic Courtès
2011-02-11 17:16     ` Andy Wingo
2011-02-12 10:13       ` 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=m37hd6egbu.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).