unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: bug-guile@gnu.org, Rob Browning <rlb@defaultvalue.org>
Subject: Re: 1.6.5 build failure: libguile-ltdl.so.1: No such file or directory
Date: Tue, 21 Dec 2004 13:55:24 -0500	[thread overview]
Message-ID: <m33bxzscp9.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m33bzf13p2.fsf@multivac.cwru.edu> (Paul Jarc's message of "Fri,  12 Nov 2004 10:34:11 -0500")

The libtool changes in 1.6.7 seem to have fixed this.


paul


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


  reply	other threads:[~2004-12-21 18:55 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
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 [this message]
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=m33bxzscp9.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    --cc=bug-guile@gnu.org \
    --cc=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).