David Abrahams wrote:
Christoph Ludwig <cludwig@cdc.informatik.tu-darmstadt.de> writes:
BTW, I was told that if boost/config.hpp is included before any system headers, it will still be able to use _REENTRANT to detect if -pthread was specified on the command line.
That's correct AFAICT, but does not really help. There's already too much code that includes system headers before any boost headers.
If we're in the same situation as Python, which requires "python.h" be included before any system headers, it's a damn shame.
That's true.
I don't understand all the reasons for this situation -- is it POSIX's fault?
No, it's gcc's fault. See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11953
Can we get them to fix this? AFAICT it's almost impossible to formulate consistent rules for using libraries together now. If someone wants to use python and boost together, what should she do?
She's out of luck, I'm afraid. We can only hope that gcc developers will fix this, and I don't know how we can affect the issue's priority... - Volodya