C++11 enabling in F22?
tim at niemueller.de
Mon Oct 26 12:50:51 UTC 2015
As the reporter let me briefly phrase the main concerns:
- the driver works only with software which is built for the same ABI,
it is one of the cases where things break immediately otherwise
- we ran into this problem when building 3rd-party software (referee box
of the RoboCup Logistics League competition). This requires C++11 for
other dependencies and therefore does not build with mongo-cxx-driver on
- we will have this problem again for the upcoming release of Fawkes,
that uses mongodb and requires C++11 in some places
- at this time, we cannot upgrade to anything beyond F22
- there are only two packages which depend on mongocxx-driver:
- iwhd: broken, as soon as MongoDB used crashes. This is not due ABI
incompatibility, but because it is not properly initializing the
library -- but in either case needs an update to actually work
- uwsgi plugins: these are explicitly built with -std=c++11 (cf.
plugins/gridfs/uwsgiplugin.py in the prep'ed package)
I have not run this myself to be fair, but given the different ABI
it will break, cf. https://jira.mongodb.org/browse/CXX-558
Therefore, no depending package currently works with this driver out of
the box. Since we need to make changes to all packages anyway, my
suggestion is to upgrade to the latest upstream release and enable C++11
to be future-proof. Within our eco-systems things are as of now broken
(iwhd, uwsgi) or prevent an upgrade/full feature set (fawkes).
I hope that this is convincing enough to make a clean cut and enable
C++11 in mongo-cxx-driver.
On 26.10.2015 12:13, Marek Skalický wrote:
> Hello everyone,
> I would like to ask what do you think about enabling c++11 in library in
> F22? Is it permitted by Fedora guidelines?
> I am asking because of this bug -
> https://bugzilla.redhat.com/show_bug.cgi?id=1274307 . And I want to know
> the opinion of someone else, to decide.
> Thank you,
More information about the devel