Hi, Could you please take a look at the attached fixinclude patch that addresses the problem:
" We have test fail for gcc.dg/cpp/trad/include.c on Android. The reason for that is that -ftraditional-cpp is not expected to work on Android due to variadic macro (like #define __builtin_warning(x, y...)) in standard headers and traditional preprocessor cannot handle them." is it ok for trunk? thanks, Alexander 2013/1/9 Andrew Pinski <pins...@gmail.com>: > On Wed, Jan 9, 2013 at 7:14 AM, Alexander Ivchenko <aivch...@gmail.com> wrote: >> Hi, >> >> We have test fail for gcc.dg/cpp/trad/include.c on Android. The >> reason for that is that >> -ftraditional-cpp is not expected to work on Android due to variadic >> macro (like #define __builtin_warning(x, y...)) >> in standard headers and traditional preprocessor cannot handle them. >> The attached patch disables that test. > > It sounds like it is better to fix the system headers instead. Via a > fixincludes for older headers and have the android folks fix them for > newer releases. > > Thanks, > Andrew Pinski
trad_cpp_fixincludes_01.patch
Description: Binary data
