On 2016-01-20 03:07, Martin Michlmayr wrote: > Usertags: ftbfs-gcc-6 gcc-6-reference-ambiguous
> You may be able to find out more about this issue at > https://gcc.gnu.org/gcc-6/changes.html >> g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../source/backend -I../source/base >> -I../source/frontend -I../unix -I../vfe -I../vfe/unix -I/usr/include/SDL >> -D_GNU_SOURCE=1 -D_REENTRANT -pthread -I/usr/include/OpenEXR -Wdate-time >> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -I/usr/include -pipe >> -Wno-multichar -Wno-write-strings -fno-enforce-eh-specs -g -O2 >> -fstack-protector-strong -Wformat -Werror=format-security -O3 -pthread -c -o >> backend/math/hcmplx.o backend/math/hcmplx.cpp >> In file included from ./backend/control/messagefactory.h:39:0, >> from ./backend/frame.h:58, >> from backend/scene/atmosph.cpp:35: >> ./backend/control/renderbackend.h:112:34: error: template argument 2 is >> invalid >> map<SceneId, shared_ptr<Scene> > scenes; Hi Martin, I haven't looked into this, yet, but the most prominent change seems to be the default switch to -std=c++14. Have you tried rebuilding the failing packages with g++-6 -std=c++11/c++03/c++98/.../gnuXX (not sure whether the old ones are correctly spelled) to see if that succeeds somewhere? If additionally information is given like "But it builds successfully with g++6 -std=c++11" or "And it also fails with g++-6 -std=c++AA/BB/CC/gnuXX/YY/ZZ" that should narrow the place where to start looking for this problem. Andreas ... and now I'm thinking how to write a pbuilder hook that switches gcc/g++ to -6 on-the-fly without having experimental enabled for the actual build
