C++ gcc 4.9定义错误

C++ gcc 4.9定义错误,c++,compiler-errors,c-preprocessor,gcc4.9,C++,Compiler Errors,C Preprocessor,Gcc4.9,下一行 # define always_inline __attribute__((always_inline)) 包含在另一个包含的文件中,并受到gcc 4.9的投诉: inc/compiler.h:98:40: error: '__always_inline__' was not declared in this scope # define always_inline __attribute__((always_inline))

下一行

#  define always_inline __attribute__((always_inline))
包含在另一个包含的文件中,并受到gcc 4.9的投诉:

inc/compiler.h:98:40: error: '__always_inline__' was not declared in this scope
 #  define always_inline __attribute__((always_inline))
                                        ^
奇怪的是,同一个头文件compiler.h包含在另一个成功编译的源文件中。有什么想法吗?编辑:我只是确保always_inline不是预定义的。供参考:

> g++ -v
Using built-in specs.
COLLECT_GCC=/opt/local/bin/g++-mp-4.9
COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin13/4.9.0/lto-wrapper
Target: x86_64-apple-darwin13
Configured with: /opt/local/var/macports/build/_opt_mports_dports_lang_gcc49/gcc49/work/gcc-4.9-20140406/configure --prefix=/opt/local --build=x86_64-apple-darwin13 --enable-languages=c,c++,objc,obj-c++,fortran,java --libdir=/opt/local/lib/gcc49 --includedir=/opt/local/include/gcc49 --infodir=/opt/local/share/info --mandir=/opt/local/share/man --datarootdir=/opt/local/share/gcc-4.9 --with-local-prefix=/opt/local --with-system-zlib --disable-nls --program-suffix=-mp-4.9 --with-gxx-include-dir=/opt/local/include/gcc49/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local --with-cloog=/opt/local --enable-cloog-backend=isl --disable-cloog-version-check --enable-stage1-checking --disable-multilib --enable-lto --enable-libstdcxx-time --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket --with-pkgversion='MacPorts gcc49 4.9-20140406_0'
Thread model: posix
gcc version 4.9.0 20140406 (experimental) (MacPorts gcc49 4.9-20140406_0) 

编译的意思是没有定义符号uu总是u内联的,您定义的是符号总是u内联的。
我的编译器.h arm\atmel studio具有定义为定义\uuuuu始终\uu内联\uuuuu属性\uuuuuuuuuuuuu始终\uuuu内联\uuuu

您在定义宏的行上收到了错误消息?如果编译一个只包含这一行的foo.c文件,会发生什么?那句台词上可能有一些有趣的人物吗?前一行的尾随反斜杠?@KeithThompson正如我所说的:在以前成功的编译中包含了相同的头…是的,但值得一试。它是如何使用的?文件的gcc-E是否给出了宏的正确预期替换?gcc不应该以这种方式遵守宏,因为它只是一个宏。