From: Andy Wingo <wingo@pobox.com>
To: Douglas Mencken <dougmencken@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: guile build problem with gcc 4.6.0
Date: Sun, 13 Mar 2011 20:26:15 +0100 [thread overview]
Message-ID: <m3bp1e4yaw.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTi=_Bic62AArTRZZWHpvYW6BBoD3viUMwG53ad0L@mail.gmail.com> (Douglas Mencken's message of "Sat, 12 Mar 2011 16:49:13 +0100")
On Sat 12 Mar 2011 16:49, Douglas Mencken <dougmencken@gmail.com> writes:
> GC 4.6.0 introduced new warning: unused-but-set-variable, so with
> -Werror it's now impossible to build guile.
This will generally be the case as new warnings are added, of course.
Can you send a log of "make -k" ? Then we can fix them all in one go.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-13 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 15:49 guile build problem with gcc 4.6.0 Douglas Mencken
2011-03-13 19:26 ` Andy Wingo [this message]
2011-03-14 16:51 ` Douglas Mencken
2011-03-17 10:46 ` Andy Wingo
2011-03-17 16:58 ` Ludovic Courtès
2011-03-20 19:11 ` Douglas Mencken
2011-03-20 20:13 ` 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=m3bp1e4yaw.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@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).