From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: bug-guile@gnu.org
Subject: Re: (dynamic-link) ignores PREFIX/lib and $LD_LIBRARY_PATH
Date: Tue, 18 Jun 2002 11:13:28 -0700 [thread overview]
Message-ID: <E17KNTs-0005Hp-00@giblet> (raw)
In-Reply-To: <m3r8j4qxjq.fsf@multivac.cwru.edu> (prj@po.cwru.edu)
From: prj@po.cwru.edu (Paul Jarc)
Date: Tue, 18 Jun 2002 13:57:39 -0400
but it would still be nice if guile could tell libtool where to look
for libguilereadline.la, since it's known to be in PREFIX/lib.
yes. btw, another (smaller scope) fix would be to munge readline.scm
`dynamic-link' call.
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-06-18 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 16:02 (dynamic-link) ignores PREFIX/lib and $LD_LIBRARY_PATH Paul Jarc
2002-06-18 17:57 ` Paul Jarc
2002-06-18 18:13 ` Thien-Thi Nguyen [this message]
2002-06-18 18:01 ` Thien-Thi Nguyen
2002-06-18 18:13 ` Paul Jarc
2002-06-18 18:37 ` Thien-Thi Nguyen
2002-06-18 21:26 ` Marius Vollmer
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=E17KNTs-0005Hp-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--cc=ttn@glug.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).