From: Rob Browning <rlb@defaultvalue.org>
Subject: libguile-ltdl updated to libtool 1.5 source in Guile 1.6 branch.
Date: Sun, 12 Oct 2003 13:53:43 -0500 [thread overview]
Message-ID: <87n0c6e18o.fsf@raven.i.defaultvalue.org> (raw)
As far as I know, this just leaves integrating any remaining cygwin
patches before we can release 1.6.5.
Also, here's something I just mentioned in another post that bears
repeating (in case people aren't watching that thread):
... for all those hacking on libguile-ltdl -- bear in mind that the
upstream/*.diff files 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 uninteresting outside of Guile.
For those interested:
2003-10-12 Rob Browning <rlb@defaultvalue.org>
* raw-ltdl.c: merged changes from libtool 1.5. Looks like most of
our bugfixes have been incorporated upstream.
* upstream/ltdl.c: update to libtool 1.5 version.
* upstream/ltdl.c.diff: added.
* upstream/ltdl.h.diff: added.
* upstream/Makefile.am (ltdl.h.diff): cleanup temp files.
(ltdl.c.diff): cleanup temp files.
* upstream/.cvsignore: remove ltdl.c.diff and ltdl.h.diff -- these
should probably be in the source tree so we're more likely to
notice any unintentional changes, and so it's easier for people to
find the diffs.
--
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
reply other threads:[~2003-10-12 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87n0c6e18o.fsf@raven.i.defaultvalue.org \
--to=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).