unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Douglas Mencken <dougmencken@gmail.com>
Cc: 14421@debbugs.gnu.org
Subject: bug#14421: Unable to build Guile 2.0.9
Date: Thu, 13 Jun 2013 16:54:57 -0400	[thread overview]
Message-ID: <87obb9enoe.fsf@tines.lan> (raw)
In-Reply-To: <8738tg863e.fsf@pobox.com> (Andy Wingo's message of "Tue, 21 May 2013 21:51:01 +0200")

Andy Wingo <wingo@pobox.com> writes:

> On Tue 21 May 2013 17:35, Douglas Mencken <dougmencken@gmail.com> writes:
>
>>   GEN      guile-procedures.texi
>> Assertion failure: reclaim.c:244
>
> reclaim.c is in libgc.  This means you have a broken libgc installation.

Douglas, did you run Boehm GC's "make check"?  What version of GC is it?
I recommend version 4.2d.

      Mark





      reply	other threads:[~2013-06-13 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18 21:05 bug#14421: Unable to build Guile 2.0.9 Douglas Mencken
2013-05-20 18:44 ` Andy Wingo
     [not found]   ` <CACYvZ7ivLmSVir2fczfq4Ngsg8TJf5PAf=TheHiUqk=KvDPcVw@mail.gmail.com>
2013-05-21 19:51     ` Andy Wingo
2013-06-13 20:54       ` Mark H Weaver [this message]

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=87obb9enoe.fsf@tines.lan \
    --to=mhw@netris.org \
    --cc=14421@debbugs.gnu.org \
    --cc=dougmencken@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).