From: Ben Noordhuis <info@bnoordhuis.nl>
To: 13416@debbugs.gnu.org
Subject: bug#13416: closed (Re: bug#13416: guile e0c211b segfaults when linked against libgc 7.1)
Date: Fri, 8 Mar 2013 09:12:05 +0100 [thread overview]
Message-ID: <CAHQurc9NMUVj8=Gb-_edJtd3GhZGqH02YqE3wqhmngRe_3Veow@mail.gmail.com> (raw)
In-Reply-To: <handler.13416.D13416.136269433419972.notifdone@debbugs.gnu.org>
On Thu, Mar 7, 2013 at 11:13 PM, GNU bug Tracking System
<help-debbugs@gnu.org> wrote:
>> 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.
I ran configure and make on a fresh clone so that can't have been it.
That said, some months have passed now and the system where I ran into
this issue has been upgraded wholesale. I can't help you in tracking
it down further.
prev parent reply other threads:[~2013-03-08 8:12 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
[not found] ` <handler.13416.D13416.136269433419972.notifdone@debbugs.gnu.org>
2013-03-08 8:12 ` Ben Noordhuis [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='CAHQurc9NMUVj8=Gb-_edJtd3GhZGqH02YqE3wqhmngRe_3Veow@mail.gmail.com' \
--to=info@bnoordhuis.nl \
--cc=13416@debbugs.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).