Red Hat Bugzilla – Bug 1478329
boost ticket 12748: Boost.Test defines a variable called VERSION
Last modified: 2017-08-13 16:53:49 EDT
As stated in the boost ticket, boost-test in boost 1.63 introduced a variable called "VERSION" which clashes with macro "VERSION" from config.h generated by autotools. Would it be possible to backport the following fix to Fedora 26? It seems to be fixed in boost 1.64.
I solved this problem on my development machine simply by editing the offending boost header manually, but obviously that's not gonna work for anybody else trying to build our software on Fedora 26. Another obvious workaround is to stick "#undef VERSION" before including that boost header, which is an ugly workaround and which I would like to avoid if possible.
Version-Release number of selected component (if applicable):
# rpm -q boost-devel
That's a pretty silly design error in Boost.Test, but I'm concerned about backporting the whole patch. Those variables are part of the public API of the library, e.g. LOG_LEVEL is documented at http://www.boost.org/doc/libs/1_63_0/libs/test/doc/html/boost_test/test_output/logging_api/log_ct_log_level.html
I think we can safely rename VERSION, because that seems to be for internal use only.
(In reply to Jonathan Wakely from comment #1)
Anything you can do would be appreciated. It's just the "VERSION" variable causing the problems. There's definitely no need to backport the whole thing.
boost-1.63.0-6.fc26 is building now:
boost-1.63.0-6.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-019deba4e2
boost-1.63.0-6.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.