I think this is an issue building Python 3.5 with gcc 4.9.2 as I've also
reproduced this on a clean Jessie amd64 VM. Up to you whether you want to
close it - should I cc the backports list?

Reply via email to