unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: bug#10093: Problem compiling related to block-growth-factor fluid
Date: Wed, 23 Nov 2011 15:06:19 +0100	[thread overview]
Message-ID: <87pqgj0w84.fsf@gnu.org> (raw)
In-Reply-To: 87hb1vnjdm.fsf@pobox.com

Hello!

Andy Wingo <wingo@pobox.com> skribis:

> On Mon 21 Nov 2011 14:35, rixed@happyleptic.org writes:
>
>> Here is a minimal example reproducing the problem.
>> Note that it only fails the first time (when scheme.scm is compiled).
>
> Fixed in stable-2.0.  Thanks for the report!

So what was the deal?  One thread would see an uninitialized fluid,
right?

Thanks,
Ludo’.




  reply	other threads:[~2011-11-23 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  9:26 Problem compiling related to block-growth-factor fluid rixed
2011-11-21 10:43 ` rixed
2011-11-21 13:35   ` rixed
2011-11-23 11:55     ` bug#10093: " Andy Wingo
2011-11-23 14:06       ` Ludovic Courtès [this message]
2011-11-23 15:27         ` Andy Wingo
2011-11-23 18:13           ` 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=87pqgj0w84.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-user@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).