From: Andy Wingo <wingo@pobox.com>
To: Ben Noordhuis <info@bnoordhuis.nl>
Cc: 13416-close@debbugs.gnu.org
Subject: bug#13416: guile e0c211b segfaults when linked against libgc 7.1
Date: Thu, 07 Mar 2013 23:11:29 +0100 [thread overview]
Message-ID: <87boaudfn2.fsf@pobox.com> (raw)
In-Reply-To: <CAHQurc_KuzF_8caCQGoRyrZgKJ1g47W+C7bGkA9ebYn_beuxpg@mail.gmail.com> (Ben Noordhuis's message of "Sat, 12 Jan 2013 03:22:31 +0100")
On Sat 12 Jan 2013 03:22, Ben Noordhuis <info@bnoordhuis.nl> writes:
> gc.c:212:1: warning: 'GC_get_free_space_divisor' defined but not used
This comes (I think) from configuring Guile against one version of
libgc, then upgrading or downgrading libgc, and then running "make"
without reconfiguring.
Closing as not a bug.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-03-07 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 2:22 bug#13416: guile e0c211b segfaults when linked against libgc 7.1 Ben Noordhuis
2013-03-07 22:11 ` Andy Wingo [this message]
[not found] ` <handler.13416.D13416.136269433419972.notifdone@debbugs.gnu.org>
2013-03-08 8:12 ` bug#13416: closed (Re: bug#13416: guile e0c211b segfaults when linked against libgc 7.1) Ben Noordhuis
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=87boaudfn2.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=13416-close@debbugs.gnu.org \
--cc=info@bnoordhuis.nl \
/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).