Slackware Linux (current tree), gcc 4.8.1, glibc 2.17

i can confirm this...

from what i read, this seems like a boost bug in 1.54 (iinm 1.53 does not have this issue).

as a package maintainer of a distro, can i suggest a new feature for oqgraph? ==> "stop using boost" it's been kind of a PITA for us...

to my untrained eye, this looks like a bad header dependency in boost...

chat of some people who might have some insight in this issue.

10:41 < zao> Well, what static-assert is it tripping on?
10:43 < zao> See named_graph.hpp:318 for a long and descriptive string
10:43 < zao> BOOST_STATIC_ASSERT_MSG
((boost::is_base_of<boost::graph_detail::stable_tag,
VertexIterStability>::value), "Named graphs cannot use vecS as
vertex container and remove vertices; the lack of vertex
descriptor stability
10:43 < zao> (which iterator stability is a proxy for) means that the name ->
vertex mapping would need to be completely rebuilt after each deletion. See
https://svn.boost.org/trac/boost/ticket/7863 for more information
and a test case.");
10:45 < zao> neoclust: The bug indicates that this has been the cause of
subtly broken behaviour in the past and that the assert is there to cause a
hard compile-time failure instead.

Acknowledged. Boost appears to cause some kind of new build issue with every new version...
I also appreciate the sentiment "stop using Boost".
We've looked at that option, but haven't found anything viable yet.

This issue may resolve when we merge OQGRAPHv3 into MariaDB 10.0, Andrew McDonnell reports that it builds with Boost 1.54 without hassle.

Fixing it in 10.0 is good, but I'd really prefer having this fixed in 5.5 as well. As it stands 5.5 is shipped with quite some distributions and unless it's fixed there too oqgraph will have to be disabled (where affected) until MariaDB is updated to 10.0.x

will mariadb 10 be final before september? cause that's the date i need to be careful of...

if so, i can just switch to mariadb 10 and don't have any issue anymore...

if not, i'll have to try to get boost 1.53 embedded inside mariadb-5.5

I guess this isn't fixed for .33 yet, as fix target seems to be .34?

Here is a possible fix as patches: https://github.com/ottok/pkg-mariadb/pull/1
Background: https://lists.launchpad.net/oqgraph-dev/msg00257.html

I assume Andrew will push this upstream soon?

I've added a test to CMakeLIsts.txt to disable OQGraph v2 (in 5.5) for incompatible Boost versions.

The quagmire of Boost for 5.5 is a ghost we'd rather not chase. There are other problems with oqgraph v2 anyhow, which is why v3 was created.

v3 appears more tolerant with Boost versions, but in any case if version-specifics need to be chased it would make sense to do so for MariaDB 10.0 and not 5.x.

AL13N you can technically have an embedded Boost in your build tree, this is how we started - however Boost/BGL is lots of files so this didn't create happiness. Therefore we didn't put it in the repo.

So, you could drop it in and make sure the build system can find it, but perhaps a better solution is to pin a specific version of Boost in your Linux install, if you find that the default/latest version has a problem. That way you can create a stable build environment without too much mess.

Please do report when a v3 has issues with specific versions of Boost, that's really important for us to track. thanks!

Thanks for the info arjen!

I did indeed drop Boost and thus OQGgraph completely for MariaDB 5.5 (in Debian) as there is no compatible libboost-dev version available, while functional versions of Boost, Judy and OQGraph are present in MariaDB 10.0 (in Debian).

For details see the contents of 'control' and 'mariadb-server-x.x.install' files in debian/*
http://anonscm.debian.org/gitweb/?p=pkg-mysql/mariadb-5.5.git
http://anonscm.debian.org/gitweb/?p=pkg-mysql/mariadb-10.0.git

Note that your comments about custom build environments don't apply here. Everything in Debian and Ubuntu are build using their standard build robots, and we cannot customize anything else than the contents of our own package.

"Fixed" by adding a test in the CMakeLists.txt — now oqgraph is disabled on incompatible boost versions

Serg - I can't find that info, can you please give the file path for that and/or paste the version info here?
I've looked in /engine/oqgraph/CMakeLists.txt

This is the revision with the fix: http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/4045

I didn't hard-code Boost versions (iirc 1.52 works and 1.53 doesn't), but extended try-compile check to include that piece of code that failed to compile on newer Boost.