From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org, Guile Mailing List <guile-user@gnu.org>
Subject: Re: Guile 1.5.6 beta available for testing.
Date: 15 Mar 2002 21:54:45 +0100 [thread overview]
Message-ID: <87adt9mu0a.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0203112051530.2317-100000@ariel.lan.telltronics.org>
Steve Tell <tell@telltronics.org> writes:
> As near as I can tell by wading through the libtool script and sh -x
> output, libtool adds "-L/usr/lib" because libguile.la says that libguile
> needs /usr/lib/libltdl.la, and /usr/lib/libltdl.a says that libltdl has
> its further dependendencies specified as "-ldl" (instead of as an absolute
> path to a libdl.la?)
Ahh, that makes sense. That is, it explains what you are seeing, but
it certainly looks wrong.
> I'm temporarily joining the libtool list to see if any of the
> experts can shed some light. It definitely looks like libtool is
> doing the wrong thing, or at least a less correct thing.
Yes, I'll listen in to the discussion on the libtool list...
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-15 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0203112051530.2317-100000@ariel.lan.telltronics.org>
2002-03-12 16:19 ` Guile 1.5.6 beta available for testing Rob Browning
2002-03-15 20:54 ` Marius Vollmer [this message]
[not found] <m38z8xly2v.fsf@appel.lilypond.org>
2002-03-12 16:23 ` Rob Browning
2002-03-15 20:57 ` 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=87adt9mu0a.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).