On my hardened ~amd64 machine I see the following failure after upgrading boost. In file included from /var/tmp/portage/games-strategy/freeorion-0.4.5/work/freeorion-0.4.5/util/SerializeUniverse.cpp:8:0: /usr/include/boost/archive/detail/iserializer.hpp: In instantiation of ‘static void boost::archive::detail::heap_allocation<T>::doesnt_have_new_operator::invoke_delete(T*) [with T = Ship]’: /usr/include/boost/archive/detail/iserializer.hpp:265:33: required from ‘static void boost::archive::detail::heap_allocation<T>::invoke_delete(T*) [with T = Ship]’ /usr/include/boost/archive/detail/iserializer.hpp:273:26: required from ‘boost::archive::detail::heap_allocation<T>::~heap_allocation() [with T = Ship]’ /usr/include/boost/archive/detail/iserializer.hpp:294:36: required from ‘void* boost::archive::detail::pointer_iserializer<Archive, T>::heap_allocation() const [with Archive = boost::archive::binary_iarchive; T = Ship]’ /var/tmp/portage/games-strategy/freeorion-0.4.5/work/freeorion-0.4.5/util/SerializeUniverse.cpp:326:133: required from here /var/tmp/portage/games-strategy/freeorion-0.4.5/work/freeorion-0.4.5/util/../universe/Ship.h:99:5: error: ‘virtual Ship::~Ship()’ is protected ~Ship() {} ^ In file included from /usr/include/boost/archive/detail/interface_iarchive.hpp:22:0, from /usr/include/boost/archive/detail/common_iarchive.hpp:23, from /usr/include/boost/archive/basic_binary_iarchive.hpp:30, from /usr/include/boost/archive/binary_iarchive_impl.hpp:21, from /usr/include/boost/archive/binary_iarchive.hpp:20, from /var/tmp/portage/games-strategy/freeorion-0.4.5/work/freeorion-0.4.5/util/Serialize.h:5, from /var/tmp/portage/games-strategy/freeorion-0.4.5/work/freeorion-0.4.5/util/SerializeUniverse.cpp:1: /usr/include/boost/archive/detail/iserializer.hpp:246:17: error: within this context delete t; ^
Created attachment 435572 [details] emerge --info
Created attachment 435574 [details] build log
why have this game been marked as old? Does that men it would not see a fix for this problem? I do confirm problem exists and that the game is far from old as changes to it are made daily https://github.com/freeorion/freeorion/commits/master although I am not sure if fix for this is already present in git.
(In reply to Wojciech Myrda from comment #3) > why have this game been marked as old? Does that men it would not see a fix > for this problem? AFAIK the '[OLD]' is because of the recent restructuring of bugzilla components and has nothing to do with this concrete bug.
same happened at tinderbox image ~/images?/amd64-desktop-unstable_20160629-232404
If I read upstream bug report right https://github.com/freeorion/freeorion/commits/master v0.4.5 would not compile & work with boost 1.61
The bug would get more attention if it was assigned to the maintainer... Would a hard requirement on <boost-1.61 help people? I guess no, since nobody wants to downgrade boost.
I reported the bug upstream, but currently the discussion there is inconclusive. The blocker is not nice, but the only option I currently see working.
Created attachment 443818 [details, diff] patch freeorion to work with boost-1.61 Applying this patch in conjuction with the CPPFLAG -DBOOST_OPTIONAL_CONFIG_USE_OLD_IMPLEMENTATION_OF_OPTIONAL worked for me (as per discussion in upstream issue).
Created attachment 443820 [details] working ebuild This ebuild adds the flag from the previous comment and inserts epatch_user for utilizing the patch.
In freeorion-0.4.5-r1 I implemented this patch and removed the dependency on "glew" which I think was wrong (only needed on Windows). Thanks for all your work. There is still the removal of the games.eclass and bump to EAPI=6 pending for this ebuild. I don't have time to look into it. Games eclass had a convenient function that writes a wrapper script. We need to replicate that functionality in the new ebuild. Please email me if you are interested to work on it.
