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 19:31:28 +0200 [thread overview]
Message-ID: <87wubnmtqn.fsf@peder.flower> (raw)
In-Reply-To: <87zngj7gvw.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 02 Oct 2003 11:18:11 -0500")
Rob Browning writes:
> Would updating the 1.6 branch using the latest libtool help
Yes.
> did you just libtoolize to get the latest bits of everything but
> libltdl, or did you merge the upstream libltdl changes into
> libguile-ltdl as well?
Yes, that was the 'annoying bit'. I checked and found that most
changes in ./upstream had been merged into libtool already. It went
something like:
patching file ltdl.c
Hunk #3 succeeded at 124 (offset 32 lines).
Hunk #4 FAILED at 192.
Hunk #5 succeeded at 389 (offset 54 lines).
Hunk #6 FAILED at 435.
Hunk #7 succeeded at 478 with fuzz 2 (offset 51 lines).
Hunk #8 FAILED at 870.
Hunk #9 FAILED at 2036.
Hunk #10 FAILED at 2782.
Hunk #11 FAILED at 3048.
Hunk #12 FAILED at 3075.
7 out of 12 hunks FAILED -- saving rejects to file ltdl.c.rej
[headache]
The only sensible change that was not yet in, as far as I could see,
was to avoid a type warning:
- dest[i] = src[i];
+ ((char *) dest)[i] = ((char *) src)[i];
With the next version of libtool, I merely updated ltdl.c and ltdl.h
from libtool CVS, as were in the previous patch I sent. Attached
seperately now.
> Also do you follow libtool upstream well enough to have a sense that
> libtool CVS is be stable enough for a 1.6 point release for all our
> other platforms?
No, I just updated when requested for new Cygwin packages. With
libtool+Cygwin it's been: fresher checkouts, more stable ;-)
Maybe best to ask the libtool developers. 1.5.1 was released on
August 8, and there was only one Cygwin patch after that, so upgrading
to that would already help a lot.
> Unfortunately, we didn't really have an alternative. We can still use
> libtoolize to bring the guile tree up to date; we just can't use the
> upstream libltdl until/unless they've fixed the important bugs.
You mean one can do 'libtoolize' but not 'libtoolize --ltdl', but that
doesn't help me.
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 17:31 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 [this message]
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=87wubnmtqn.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).