From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-devel@gnu.org, hanwen@cs.uu.nl
Subject: Cygwin patch for 1.6.4 [WAS: When is 1.8 going to be released]
Date: Wed, 01 Oct 2003 21:57:59 +0200 [thread overview]
Message-ID: <87u16s7mt4.fsf@peder.flower> (raw)
In-Reply-To: <16225.62509.832674.84224@localhost.localdomain> (Han-Wen Nienhuys's message of "Fri, 12 Sep 2003 18:28:29 +0200")
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Han-Wen Nienhuys writes:
>> However, Jan is getting annoyed at having to patch GUILE to get it
>> compiling on cygwin.
>
> I'm not aware of Cygwin patches (which is enterily my fault).
Well, I sent patches for cross compilation and Cygwin just before 1.6:
http://mail.gnu.org/archive/html/guile-devel/2002-07/msg00014.html
and they were, with some small modifications, included in HEAD. So,
strictly speaking there are no pending patches but rather a small
1.6.x annoyance.
It should have been OK for me to patch guile-1.6.x for Cygwin, had it
not been for the fact that my build process for Cygwin included:
libtoolize --force --copy --automake --ltdl
(using a Cygwin prerelease or libtool CVS), because libtool is under
active development for Cygwin. This broke when guile included a
modified copy of libtool in 1.6.x.
> Please mail them to me and I'll have a look.
Attached. The biggest part is the libtool diff, you'll want to skip
that and just look at the small upstream/ltdl*diff instead.
Also note that most of this is in HEAD and some of it has already been
modified again a few months ago.
Greetings,
Jan.
[-- Attachment #2: guile-1.6.4-cygwin.gz --]
[-- Type: application/octet-stream, Size: 28315 bytes --]
[-- Attachment #3: Type: text/plain, Size: 141 bytes --]
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2003-10-01 19:57 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 ` Jan Nieuwenhuizen [this message]
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
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=87u16s7mt4.fsf@peder.flower \
--to=janneke@gnu.org \
--cc=guile-devel@gnu.org \
--cc=hanwen@cs.uu.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).