From: ludo@gnu.org (Ludovic Courtès)
To: Patrick McCarty <pnorcks@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Backward compatibility status
Date: Mon, 15 Mar 2010 00:38:42 +0100 [thread overview]
Message-ID: <87y6hu8oe5.fsf@gnu.org> (raw)
In-Reply-To: <d1c3ee7b1003141612p35004be1tbfa01f5e6dd42587@mail.gmail.com> (Patrick McCarty's message of "Sun, 14 Mar 2010 16:12:43 -0700")
Hi Patrick,
Patrick McCarty <pnorcks@gmail.com> writes:
> 2010/3/6 Ludovic Courtès <ludo@gnu.org>:
[...]
>> | Name | Cause |
>> |---------------------------------------+-------------------------------------------------|
>> | lilypond-2.13.9 | `scm_internal_hash_fold' & `scm_t_hash_fold_fn' |
>
> Is this something that should be fixed in LilyPond?
I think so, yes (especially since ‘scm_internal_hash_fold’ was intended
to be sort-of internal.)
> For reference, I'm fairly certain this build failure was introduced
> with Guile commit a07010bf1828704edd9a40cadb0eaf820b8f3638.
Yes, that’s the one.
> If I add the typedefs to the appropriate LilyPond header file and use
> them, the problem goes away, but I don't know if there are unexpected
> side effects of this.
I think you want a fix that retains compatibility with 1.8. How about
having a ‘configure’ test checking for this typedef?
> I am unable to test any further, because there are more build failures
> down the pipeline. :-)
Heh. Let us know what other Guile-related failures you stumble upon!
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-03-14 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 0:29 Backward compatibility status Ludovic Courtès
2010-03-14 23:12 ` Patrick McCarty
2010-03-14 23:38 ` Ludovic Courtès [this message]
2010-03-20 22:06 ` Ian Hulin
2010-03-20 22:35 ` Ludovic Courtès
2010-04-02 18:21 ` Patrick McCarty
2010-04-05 17:06 ` Ludovic Courtès
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=87y6hu8oe5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=pnorcks@gmail.com \
/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).