From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: hanwen@cs.uu.nl, guile-devel@gnu.org, mvo@zagadka.de
Subject: Re: Cygwin patch for 1.6.4
Date: Thu, 02 Oct 2003 09:21:10 +0200 [thread overview]
Message-ID: <87d6dgksux.fsf@peder.flower> (raw)
In-Reply-To: <87d6dgbnjz.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Wed, 01 Oct 2003 17:28:16 -0500")
Rob Browning writes:
> OK, so just to make sure I follow, this is a patch against 1.6.4,
Yes,
> it would be appropriate for the upcoming 1.6.5.
Yes,
> Further, if I'm going ot apply it to 1.6 before 1.6.5, I should
> ignore the libool bits.
> Did I get that right?
Maybe, but I'm not sure what happens when you 'ignore the libtool
bits'. What I meant to say whas that I'd like to have the libtool
part of the patch in too, but that it makes the patch against 1.6.4
deceptively large. That's because I updated to libtool CVS.
The new guile diffs against libtool, generated automagically in
libguile-ltdl/upstream, are more readable, because they are very
small.
The fact that guile 1.6.x is no longer a standard libtoolized package
(where the user can upgrade libtool with a single command if
necessary) but ships a modified copy that needs some work to upgrade
is what cost me most time. But maybe I missed something.
Sorry for the confusion.
Greetings,
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-10-02 7:21 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 [this message]
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
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=87d6dgksux.fsf@peder.flower \
--to=janneke@gnu.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).