From: Markus Elfring <Markus.Elfring@web.de>
Cc: gcc-help@gcc.gnu.org, Clang <cfe-dev@cs.uiuc.edu>
Subject: Difficulties with binding to functions for semantic actions in a grammar
Date: Thu, 17 Oct 2013 14:00:00 -0000 [thread overview]
Message-ID: <525FED85.1060200@web.de> (raw)
Hello,
I stumble on another challenge during the software development of a small
application which I derive from the Spirit tutorial on my openSUSE system.
http://sourceforge.net/mailarchive/message.php?msg_id=31489573
I observe that a source file is accepted by my compilers in one build
configuration. But error messages are displayed if I switch to the build
configuration where the relevant source code is directly included by header
files. Would you like to share any ideas on approaches to resolve this issue?
https://github.com/elfring/boot_parameters/blob/d65ffb55c0643aac8cb02126066252e898b12bf9/boost/CMakeLists.txt
Regards,
Markus
next reply other threads:[~2013-10-17 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 14:00 Markus Elfring [this message]
2013-10-17 16:26 ` Ian Lance Taylor
2013-10-17 18:50 ` Markus Elfring
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525FED85.1060200@web.de \
--to=markus.elfring@web.de \
--cc=cfe-dev@cs.uiuc.edu \
--cc=gcc-help@gcc.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).