unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: jantien@xs4all.nl, guile-devel@gnu.org
Subject: Re: libguile-ltdl
Date: Thu, 07 Oct 2004 10:17:32 -0500	[thread overview]
Message-ID: <871xgay2ur.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <16740.62885.728489.705345@byrd.xs4all.nl> (Han-Wen Nienhuys's message of "Thu, 7 Oct 2004 09:52:05 +0200")

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

> rlb@defaultvalue.org writes:
>> I'd like to see what Marius thinks, but we might be able to remove
>> libguile-ltdl in 1.7 now.  I'd be more hesitant to do so in 1.6,
>> unless it was only for cygwin.  Removing a library isn't a backward
>> compatible change.
>
> Why not make it a configuration option? Then we don't throw away the
> work of infrastructure for making the forked libtool.

I'm OK with dumping libguile-ltdl altogether in 1.7, if we don't think
we're going to pursue enhancements anytime soon.  We can always add it
back later, and a --disable-libguile-ltdl option sounds like it might
be a reasonable way to handle the problem in 1.6 if the fix for
libguile-ldtl for cygwin is too hard.

Although if it's just cygwin, and if libguile-ltdl has *never* worked
there, then another alternative might be to just disable it when
cygwin is detected.

Ideally though, I'd still much rather just have a fix for
libguile-ltdl on cygwin if that were possible, and not too difficult.

-- 
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


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


  reply	other threads:[~2004-10-07 15:17 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         ` Rob Browning [this message]
2004-10-07 18:35           ` libguile-ltdl Han-Wen Nienhuys
2004-10-18 16:28       ` libguile-ltdl Marius Vollmer
2004-10-18 16:32     ` libguile-ltdl 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=871xgay2ur.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=jantien@xs4all.nl \
    /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).