unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org, Rob Browning <rlb@defaultvalue.org>
Subject: Re: libguile-ltdl
Date: Mon, 18 Oct 2004 18:32:59 +0200	[thread overview]
Message-ID: <lj1xfwyojo.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <16740.30007.983868.166131@byrd.xs4all.nl> (Han-Wen Nienhuys's message of "Thu, 7 Oct 2004 00:44:07 +0200")

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:

> The following patch solves the problem with GUILE on
> Cygwin. Essentially, it completely removes the branched version of
> ltdl from GUILE, substituting the system-installed ltdl.  Putting the
> branch into GUILE itself has caused headaches for other platforms -in
> particular, Cygwin- so I propose we stop doing it.

Yep, we can do that.  I still curious, tho, about the difference
between Cygwin libltdl and the latest released libltdl.  Can you say
something about this?


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      parent reply	other threads:[~2004-10-18 16:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 22:36 libguile-ltdl Han-Wen Nienhuys
2004-09-28 22:54 ` libguile-ltdl Rob Browning
2004-10-06 22:44   ` libguile-ltdl Han-Wen Nienhuys
2004-10-07  1:31     ` libguile-ltdl Rob Browning
2004-10-07  7:48       ` libguile-ltdl Han-Wen Nienhuys
2004-10-07 15:11         ` libguile-ltdl Rob Browning
2004-10-07  7:52       ` libguile-ltdl Han-Wen Nienhuys
2004-10-07 15:17         ` libguile-ltdl Rob Browning
2004-10-07 18:35           ` libguile-ltdl Han-Wen Nienhuys
2004-10-18 16:28       ` libguile-ltdl Marius Vollmer
2004-10-18 16:32     ` 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=lj1xfwyojo.fsf@troy.dt.e-technik.uni-dortmund.de \
    --to=marius.vollmer@uni-dortmund.de \
    --cc=guile-devel@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).