Created attachment 413682 [details] emerge --info On my hardened ~amd64 machine with gcc-5.2.0 I see the following failure for paludis. x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -pthread -Wall -Wextra -Wold-style-cast -Wredundant-decls -Wstrict-null-sentinel -Wmissing-noreturn -Woverloaded-virtual -Winit-self -Wunreachable-code -Wunused -Wunused-function -Wshadow -Wwrite-strings -Wfloat-equal -Wno-ignored-qualifiers -Wno-non-virtual-dtor -std=c++11 -ggdb -fvisibility-inlines-hidden -fvisibility=hidden -DPALUDIS_ENABLE_VISIBILITY=1 -O2 -pipe -march=native -floop-interchange -floop-strip-mine -floop-block -finline-functions -c -o collect_depped_upon.o collect_depped_upon.cc collect_depped_upon.cc: In function ‘const std::shared_ptr<const paludis::Sequence<paludis::resolver::DependentPackageID> > paludis::resolver::dependent_upon(const paludis::Environment*, const std::shared_ptr<const paludis::PackageID>&, const std::shared_ptr<const paludis::Sequence<paludis::resolver::ChangeByResolvent> >&, const std::shared_ptr<const paludis::Sequence<paludis::resolver::ChangeByResolvent> >&, const std::shared_ptr<const paludis::Sequence<std::shared_ptr<const paludis::PackageID> > >&)’: collect_depped_upon.cc:242:122: error: direct-list-initialization of ‘auto’ requires exactly one element [-fpermissive] auto k { &PackageID::build_dependencies_key, &PackageID::run_dependencies_key, &PackageID::post_dependencies_key }; ^
Created attachment 413684 [details] build log
Created attachment 418686 [details, diff] paludis-2.4.0-direct-list-initialization-c++11.patch I've tested the patch with GCC-5.3 and 4.8.5 and with both it compiled. See also http://comments.gmane.org/gmane.linux.gentoo.paludis.user/2042
same for gcc-5.3 @ amd64-hardened-unstable_20151227-13060
paludis-2.6.0 compiles successfully using gcc-5.4.0. I believe this bug report may be closed.
@arches, please stabilise so we can move on with stabilising GCC 5.
Stable on amd64.
Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa
x86 stable. Closing.