From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: 1.8 make check failing in popen.test
Date: Mon, 11 Sep 2006 07:40:21 +0100 [thread overview]
Message-ID: <87mz9629ey.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87ejujkxsr.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sun, 10 Sep 2006 18:16:20 -0700")
Rob Browning <rlb@defaultvalue.org> writes:
> On a related topic, in order for Guile 1.8 to make it into Debian etch
> (the upcoming stable release), we're essentially out of time to fix
> this problem. Because of this I'm contemplating uploading the initial
> Guile 1.8 packages with --with-threads=no.
>
> Does anyone see any major problems with this stopgap? It seems better
> to have Guile 1.8 in etch without threads than not to have it at all.
Will etch have guile 1.6 as well, or would this upload replace guile
1.6?
In any case, I think without-threads is probably OK.
> Note that this issue doesn't just affect Guile. It's my understanding
> that unless Guile 1.8 packages are uploaded very soon, the newer
> version of lilypond won't make it into etch either.
That would be serious. Presumably lilypond doesn't require threads
then?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-09-11 6:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 8:37 1.8 make check failing in popen.test Rob Browning
2006-07-23 22:36 ` Kevin Ryde
2006-07-23 23:12 ` Rob Browning
2006-07-24 7:25 ` Ludovic Courtès
2006-07-30 1:59 ` Rob Browning
2006-08-15 8:35 ` Rob Browning
2006-08-15 23:13 ` Kevin Ryde
2006-08-16 1:18 ` Rob Browning
2006-08-16 23:26 ` Kevin Ryde
2006-08-18 3:01 ` Rob Browning
2006-08-21 23:38 ` Kevin Ryde
2006-08-22 2:03 ` Rob Browning
2006-08-25 1:16 ` Kevin Ryde
2006-08-25 2:39 ` Rob Browning
2006-08-27 20:06 ` Rob Browning
2006-08-27 20:22 ` Rob Browning
2006-08-30 7:50 ` Rob Browning
2006-08-31 0:24 ` Kevin Ryde
2006-08-31 6:28 ` Rob Browning
2006-09-04 2:45 ` Rob Browning
2006-09-07 20:46 ` Kevin Ryde
2006-09-08 2:45 ` Rob Browning
2006-09-08 23:05 ` Kevin Ryde
2006-09-09 12:52 ` Marius Vollmer
2006-09-09 16:39 ` Rob Browning
2006-09-10 16:24 ` Rob Browning
2006-09-11 1:16 ` Rob Browning
2006-09-11 6:40 ` Neil Jerram [this message]
2006-09-11 15:57 ` Rob Browning
2006-09-11 17:40 ` Neil Jerram
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=87mz9629ey.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.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).