librci0.4-dev debian packaged should mark libboost-regex-dev as a dependency
compiling liboncilla (that depends on rci), needs the file libboost_regex-mt.so to be present, and packaged in package libboost-regex-dev
I would suggest to put :
Depends: libboost-regex-dev | libboost-regex1.48-dev
in the dependency of the package, or in the dependency of upstream dependencies if librci does not actually depends on that package, but one of its deps actually depend on it.
#2 Updated by A. Tuleu about 11 years ago
Why not putting libboost-regex1.48-dev as an alternative dependency ? It would allow users to install and use boost 1.48 instead of only boost 1.46 on precise ? Actually clang and boost 1.46 does not work at all, but 1.48 does.
And I would very much like use boost 1.48 and clang on precise ....
And as for quantal, 1.49 is the default, so if you continously integrate over quantal you should get it.
#4 Updated by A. Tuleu about 11 years ago
Actually I read more about all this stuff, and it seems that boost prior to 1.48.0-3 has a lot of issue with c++0X and c++11, even with just smart pointers.
The issue is that the old GCC 4.6 does not implement the complete C++11 standard, and let not this bug show up. But newer compiler does....
So Using RSC allone is OK, using RSC + NemoMath (need to use c++11), will always break with a more recent compiler.
However, for that stupid Roboard platform I need to support lucid (it stays at boost 1.40 ).... so we could not enforce on that platform boost >= 1.48.0-3
This whole issue drives me crazy .... I think I would even try to backport to lucid libboost1.48 (no really, I would like to be closer than the standard ....)
#5 Updated by A. Tuleu about 11 years ago
- Status changed from Resolved to In Progress
Sorry for lot of comments on that issue on reopening
I think that we should rather forbids compilation of rci of boost version is less than 1.48 and the compiler is either GCC 4.7 or Clang
And we should dismiss that conditionnal install, as it could lead to API break with libboost_regex and librsc
I would prepare some patch for you if you agree
#6 Updated by A. Tuleu about 11 years ago
The added patch would check at configuration time if someone is trying to use a bad compiler / boost / C++11 mix and report an error
Should be extended to see if gcc 4.7 (full C++11 support) should be tested too for boost >> 1.48.0 (1.48.0-3 is debian patched version of boost, this issue is fixed only for >> 1.48.0 in non debian world)
Maybe you could add a module in RSC for that. I will add the same with liboncilla.