From: Hattuari <susudata@setidava.kushan.aa>
Subject: c-macro-expand with C++?
Date: Thu, 02 Jun 2005 18:46:32 -0400 [thread overview]
Message-ID: <QfmdnW8UnvfWEQLfRVn-3A@speakeasy.net> (raw)
I've been trying to use c-macro-expand (for the first time in any language)
with C++ code. It doesn't seem to know how to find the standard headers.
I'm a bit confused by that since I am under the impression that GCC looks
in its own installation directories automatically.
Here's an example of what the output looks like:
In file included from /home/hattons/opt/org/osg/include/osg/StateSet:18,
from /home/hattons/opt/org/osg/include/osg/Node:19,
from <stdin>:17:
/home/hattons/opt/org/osg/include/osg/StateAttribute:21:20: typeinfo: No
such file or directory
/home/hattons/opt/org/osg/include/osg/StateAttribute:22:19: utility: No such
file or directory
/home/hattons/opt/org/osg/include/osg/StateAttribute:23:18: vector: No such
file or directory
In file included from /home/hattons/opt/org/osg/include/osg/Uniform:25,
from /home/hattons/opt/org/osg/include/osg/StateSet:21,
from /home/hattons/opt/org/osg/include/osg/Node:19,
from <stdin>:17:
/home/hattons/opt/org/osg/include/osg/GL2Extensions:24:18: string: No such
file or directory
In file included from /home/hattons/opt/org/osg/include/osg/StateSet:21,
from /home/hattons/opt/org/osg/include/osg/Node:19,
from <stdin>:17:
I tried giving it /usr/include and /usr/include/g++ (which is where I found
what look to be the standard headers.)
ls /usr/include/g++/
algorithm cctype clocale cstdarg ctime exception
i586-suse-linux istream map queue streambuf vector
backward cerrno cmath cstddef cwchar exception_defines.h iomanip
iterator memory set string
bits cfloat complex cstdio cwctype ext ios
limits new sstream typeinfo
bitset ciso646 csetjmp cstdlib cxxabi.h fstream iosfwd
list numeric stack utility
cassert climits csignal cstring deque functional
iostream locale ostream stdexcept valarray
Can this be made to work?
reply other threads:[~2005-06-02 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=QfmdnW8UnvfWEQLfRVn-3A@speakeasy.net \
--to=susudata@setidava.kushan.aa \
/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).