Aleksey Gurtovoy wrote:
The first thing I see is this:
intel-linux-C++-action ../bin/boost/libs/python/build/libboost_python.so/intel-8.0-linux/debug/shared-linkable-true/stdlib-gcc/numeric.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/include/g++-v3/limits(280): error: identifier "__CHAR_BIT__" is undefined static const int digits = __glibcpp_digits (char); ^
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/include/g++-v3/limits(330): error: identifier "__CHAR_BIT__" is undefined static const int digits = __glibcpp_digits (signed char); ^
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/include/g++-v3/limits(326): error: identifier "__SCHAR_MAX__" is undefined { return -__SCHAR_MAX__ - 1; } ^ ...
Any clues of what's up here?
Hmm, no. The __glibcpp_digits macro gets defined unconditionally in g++-v3/limits, lines 140/141. It gets undefined in line 1050 of the same file. The first error is in line 280. The error can be reproduced here with a source file that consists only of #include <limits> I'll try to look into that again tomorrow. Regards, m