From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: 1.6.5 build failure: libguile-ltdl.so.1: No such file or directory
Date: Wed, 06 Oct 2004 00:13:30 -0500 [thread overview]
Message-ID: <87brfg5szp.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <m3oejh80a6.fsf@multivac.cwru.edu> (Paul Jarc's message of "Tue, 05 Oct 2004 14:52:43 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
> Building 1.6.5 fails for me:
> ...
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/fs/home/mount/home/prj/src/spf/guile-1.6.5'
> make: *** [all] Error 2
>
> I can work around it by setting
> LD_LIBRARY_PATH="$PWD/libguile-ltdl/.libs".
I've seen something similar in 1.7, but not 1.6. Marius has looked in
to the 1.7 problem, and if I recall correctly, he said it looked like
a libtool problem. I haven't checked it myself yet.
Just out of curiousity, do you have a version of guile already
installed on that machine in the default path, and if so (and if it's
easy), are the results any different if you remove that copy of guile
(including libs) and clean/re-build 1.6.5?
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-10-06 5:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 18:52 1.6.5 build failure: libguile-ltdl.so.1: No such file or directory Paul Jarc
2004-10-06 5:13 ` Rob Browning [this message]
2004-10-06 14:20 ` Paul Jarc
2004-10-07 1:10 ` Rob Browning
2004-10-07 14:33 ` Paul Jarc
2004-11-04 13:41 ` Marius Vollmer
2004-11-12 15:34 ` Paul Jarc
2004-12-21 18:55 ` Paul Jarc
2004-12-21 19:18 ` Rob Browning
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=87brfg5szp.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).