Richard,
It is likely that an error in your own code, like a missing
semi-colon at the end of a line, occurring before the #include statement
is causing the problem. The error might not be recognized by the compiler
until it gets to the header, even though the header itself is fine.
Happ
Richard
Usually when you get an error inside a system #include file, you look at
your code, as you can easily cause your includes to generate errors. I do
it all the time ;) I would need the code in an.cc you sent the compiler to
guess at what you did to generate that error.
Can you isolate the
Richard Jones <[EMAIL PROTECTED]> writes:
> Hiya, I'm using g++ under Debian 1.2 and have the following compile error:
The problem is almost assuredly with an.cc, or some header of your
own. This compiles fine, for example:
--
#include
--
Try to cut lines out of an.cc until the problem goes a
Hiya, I'm using g++ under Debian 1.2 and have the following compile error:
g++ -O -I ./lib-c an.cc -o an.o
In file included from /usr/include/features.h:134,
from /usr/include/stdio.h:31,
from an.cc:22:
/usr/include/sys/cdefs.h:118: parse error before `typede
4 matches
Mail list logo
