From: Kevin Ryde <user42@zip.com.au>
Cc: Bruce Korb <bkorb@veritas.com>
Subject: Re: guile-1.6.5 is even worse -- on Linux, no less
Date: Sun, 28 Nov 2004 06:50:58 +1100 [thread overview]
Message-ID: <87oehjm5p9.fsf@zip.com.au> (raw)
In-Reply-To: 418532E2.7E99E9CE@veritas.com
Bruce Korb <bkorb@veritas.com> writes:
>
> The problem seems to be that, contrary to previous custom, using '='
> in a path now causes build failure.
Actually for me it happens with a directory name "bb" too, the "="
doesn't seem to be the key. But not having a libguile-ltdl.so.1 in
/usr/lib does seem to matter.
Looks like libtool's lt-guile uninstalled binary gets a NEEDED record
for libguile-ltdl.so.1 but no rpath to it. Not sure if that NEEDED is
meant to be there, it's only a sub-dependency of libguile.so.
Adding ../libguile-ltdl/libguile-ltdl.la explicitly into the guile
program link seems to help.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-11-27 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 18:35 guile-1.6.5 is even worse -- on Linux, no less Bruce Korb
2004-10-31 18:45 ` Bruce Korb
2004-11-27 19:50 ` Kevin Ryde [this message]
2004-12-14 6:17 ` Rob Browning
2004-12-15 22:52 ` Kevin Ryde
2004-12-22 16:45 ` 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=87oehjm5p9.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bkorb@veritas.com \
/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).