From: Mark H Weaver <mhw@netris.org>
To: guile-devel@gnu.org
Subject: Re: Trouble with guile-snarf and clang-3.4's preprocessor
Date: Thu, 06 Mar 2014 17:52:39 -0500 [thread overview]
Message-ID: <87y50nlz2g.fsf@yeeloong.lan> (raw)
In-Reply-To: <8761ntm35f.fsf@yeeloong.lan> (Mark H. Weaver's message of "Wed, 05 Mar 2014 03:59:56 -0500")
Mark H Weaver <mhw@netris.org> writes:
> Hello all,
>
> clang 3.4 is unable to successfully compile Guile 1.8, 2.0, or master.
> In all cases, Guile segfaults on its first execution, while trying to
> generate guile-procedures.texi.
>
> The reason is that clang 3.4's C preprocessor introduces a lot of extra
> newlines in surprising places. Our snarfing macros are unable to cope
> with this, and lots of initialization code is lost.
I pushed a fix for this to the stable-2.0 branch.
http://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=c3c3032608c9658c5dc5019d85446b6a1c2f7fcc
Mark
next prev parent reply other threads:[~2014-03-06 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 8:59 Trouble with guile-snarf and clang-3.4's preprocessor Mark H Weaver
2014-03-06 22:52 ` Mark H Weaver [this message]
2014-03-10 13:20 ` Ludovic Courtès
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=87y50nlz2g.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=guile-devel@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).