From: Francis Southern <francis.southern@gmail.com>
To: bug-guile@gnu.org
Subject: Possibly strange fluid errors
Date: Mon, 13 Jun 2011 21:57:19 +0100 [thread overview]
Message-ID: <BANLkTinNLNohPrJpyyZX_QtLf_XBW5jWJw@mail.gmail.com> (raw)
Hell Guilers,
I just built Guile from the stable-2.0 branch of the Git repository
and got these errors from running `make check':
FAIL: fluids.test: initial fluid values: fluid-ref uninitialized fluid is #f
FAIL: fluids.test: with-fluids with non-fluid: fluids not modified if
nonfluid passed to with-fluids
FAIL: fluids.test: with-fluids with duplicate fluid: original value restored
To build I ran:
git reset --hard origin/stable-2.0
git clean -fdx
git pull
./autogen.sh
./configure
make clean
make -j3
I'm using Debian 6.0.1 "Squeeze" x86_64, libgc 7.2alpha4, gcc (Debian
4.4.5-8) 4.4.5, glibc-2.11-1, basically everything is stock Debian
Stable except for libgc.
I was told on IRC that it would probably be best to report the problem
here, so here I am.
I'm happy to provide any further information that might be needed.
Francis
next reply other threads:[~2011-06-13 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 20:57 Francis Southern [this message]
2011-06-16 17:49 ` Possibly strange fluid errors Andy Wingo
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=BANLkTinNLNohPrJpyyZX_QtLf_XBW5jWJw@mail.gmail.com \
--to=francis.southern@gmail.com \
--cc=bug-guile@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).