Graph depends on xpressive, but xpressive doesn't work with Sun's compiler

[willchido@…]

Graph depends on a library does not work with Sun's compiler. The people from xpressive have declared that they will not attempt to fix the problem. Therefore, the Boost build will forever fail when the sun tool set is used, because graph depends on xpressive.

It seems like the rational thing to do would be for graph to realize that attempting to build with Sun's compiler was not going to work, and for it to remove itself from the Boost build automatically with a warning.

At the very least, this extremely predictable failure should be documented, especially since it is going to occur from now until the end of time.

This behavior has occurred since Boost version 1.44.

[viboes]

is Boost.Xpressive essential to Boost.Graph? If not I would expect that the parts depending on Boost.Xpresive can be excluded conditionaly. Could this be possible?

[Jeremiah Willcock]

There is one I/O routine that uses Xpressive, but I tried changing that to hand-written code and it didn't seem to improve portability to any compilers, so I reverted that change. Other I/O routines use PropertyTree, which seems to break some compilers as well. I can easily work around the Xpressive issue if I had a Boost.Config macro to tell when it is broken.