From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: Bruce Korb <bkorb@veritas.com>, guile-devel@gnu.org
Subject: Re: guile-1.6.5 is even worse -- on Linux, no less
Date: Wed, 22 Dec 2004 17:45:54 +0100 [thread overview]
Message-ID: <lj652ucmd9.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <87d5xdbe00.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Tue, 14 Dec 2004 00:17:03 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
> Oh, and Marius, unless you think I've misdiagnosed, I'll probably also
> revert the addition of libguile-ltdl to subdirs_with_ltlibs in
> pre-inst-guile.in.
That's fine with me.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-12-22 16:45 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
2004-12-14 6:17 ` Rob Browning
2004-12-15 22:52 ` Kevin Ryde
2004-12-22 16:45 ` Marius Vollmer [this message]
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=lj652ucmd9.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--cc=bkorb@veritas.com \
--cc=guile-devel@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).