From: Matt Sicker <boards@gmail.com>
To: 15545@debbugs.gnu.org
Subject: bug#15545: Compilation error with clang with guile 1.8.8
Date: Sun, 6 Oct 2013 14:44:32 -0500 [thread overview]
Message-ID: <CACmp6kq7XQipPScM2YFYy6Eb1R3vv=LewbfuzRiVSNte8MpeeA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 595 bytes --]
I've attached the log from running make with the autogen project (which
depends on guile). As a quick summary, the compiler issue seems to be due
to the use of the variable name "noreturn" in libguile/throw.h, line 94, in
the function declaration scm_ithrow(). As I'm not very familiar with C++11,
I don't know if this is a compiler bug on clang's end,
implementation-defined behaviour on both clang's and gcc's ends, or a
problem on your part with using a C++11 keyword as an argument name.
Also, while compiling guile itself, I get the following message:
--
Matt Sicker <boards@gmail.com>
[-- Attachment #1.2: Type: text/html, Size: 756 bytes --]
[-- Attachment #2: errs.xz --]
[-- Type: application/octet-stream, Size: 7652 bytes --]
next reply other threads:[~2013-10-06 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 19:44 Matt Sicker [this message]
2014-01-15 21:06 ` bug#15545: Compilation error with clang with guile 1.8.8 Mark H Weaver
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='CACmp6kq7XQipPScM2YFYy6Eb1R3vv=LewbfuzRiVSNte8MpeeA@mail.gmail.com' \
--to=boards@gmail.com \
--cc=15545@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).