From: Rob Browning <rlb@defaultvalue.org>
Cc: hanwen@cs.uu.nl, guile-devel@gnu.org, mvo@zagadka.de
Subject: Re: Cygwin patch for 1.6.4
Date: Sun, 12 Oct 2003 13:50:05 -0500 [thread overview]
Message-ID: <87r81ie1eq.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87wubnmtqn.fsf@peder.flower> (Jan Nieuwenhuizen's message of "Thu, 02 Oct 2003 19:31:28 +0200")
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Rob Browning writes:
>
>> Would updating the 1.6 branch using the latest libtool help
>
> Yes.
OK, I've updated the 1.6 branch to the latest stable libtool (1.5).
Could you generate a new diff against that containing what you need?
I'd prefer to stick with the stable libtool code if possible, since
it's (hopefully) better tested against all of the supported platforms.
Also, for all those hacking on libguile-ltdl -- bear in mind that
upstream/*.diff don't contain our complete diffs against the upstream
libtool source in ltdl.[hc]. When creating the diffs in
upstream/Makefile.am, we filter out a bunch of scoping related stuff
that's uniniteresting outside of Guile.
Thanks
--
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://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-10-12 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16225.62509.832674.84224@localhost.localdomain>
2003-10-01 19:57 ` Cygwin patch for 1.6.4 [WAS: When is 1.8 going to be released] Jan Nieuwenhuizen
2003-10-01 22:28 ` Cygwin patch for 1.6.4 Rob Browning
2003-10-02 7:21 ` Jan Nieuwenhuizen
2003-10-02 16:18 ` Rob Browning
2003-10-02 17:31 ` Jan Nieuwenhuizen
2003-10-02 17:34 ` Jan Nieuwenhuizen
2003-10-12 18:50 ` Rob Browning [this message]
2003-10-02 1:33 ` Kevin Ryde
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=87r81ie1eq.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=hanwen@cs.uu.nl \
--cc=mvo@zagadka.de \
/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).