Bug#810065: blender: FTBFS with python3.5 as default python3 (transition imminent)

[Scott Kitterman]

Source: blender
Version: 2.74+dfsg0-5
Severity: important

While test building blender in a sid chroot that had been modified to make
python3.5 the default python3 in preparation for the upcoming transition I got
the following FTBFS:

[ 79%] Building C object source/blender/python/generic/CMakeFiles/bf_python_ext.dir/py_capi_utils.c.o
cd /home/test/blender-2.74+dfsg0/obj-x86_64-linux-gnu/source/blender/python/generic && /usr/bin/cc  -DHAVE_STDBOOL_H -DWITH_GLU -DWITH_GL_PROFILE_COMPAT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -D__LITTLE_ENDIAN__ -D__MMX__ -D__SSE2__ -D__SSE__ -I/home/test/blender-2.74+dfsg0/source/blender/python/generic -I/home/test/blender-2.74+dfsg0/source/blender/blenkernel -I/home/test/blender-2.74+dfsg0/source/blender/blenlib -I/home/test/blender-2.74+dfsg0/source/blender/gpu -I/home/test/blender-2.74+dfsg0/source/blender/makesdna -I/home/test/blender-2.74+dfsg0/intern/guardedalloc -I/home/test/blender-2.74+dfsg0/intern/glew-mx -isystem /usr/include/python3.5m  -Wall -Wcast-align -Werror=declaration-after-statement -Werror=implicit-function-declaration -Werror=return-type -Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wlogical-op -Wundef -Winit-self -Wnonnull -Wmissing-include-dirs -
 Wno-div-by-zero -Wtype-limits -Wuninitialized -Wredundant-decls -Wno-error=unused-but-set-variable -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fopenmp  -msse2  -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing   -o CMakeFiles/bf_python_ext.dir/py_capi_utils.c.o   -c /home/test/blender-2.74+dfsg0/source/blender/python/generic/py_capi_utils.c
/home/test/blender-2.74+dfsg0/source/blender/python/generic/py_capi_utils.c: In function 'PyC_IsInterpreterActive':
/home/test/blender-2.74+dfsg0/source/blender/python/generic/py_capi_utils.c:632:28: error: implicit declaration of function '_Py_atomic_load_relaxed' [-Werror=implicit-function-declaration]
  return (((PyThreadState *)_Py_atomic_load_relaxed(&_PyThreadState_Current)) != NULL);
                            ^
/home/test/blender-2.74+dfsg0/source/blender/python/generic/py_capi_utils.c:632:53: error: '_PyThreadState_Current' undeclared (first use in this function)
  return (((PyThreadState *)_Py_atomic_load_relaxed(&_PyThreadState_Current)) != NULL);
                                                     ^
/home/test/blender-2.74+dfsg0/source/blender/python/generic/py_capi_utils.c:632:53: note: each undeclared identifier is reported only once for each function it appears in
/home/test/blender-2.74+dfsg0/source/blender/python/generic/py_capi_utils.c:633:1: error: control reaches end of non-void function [-Werror=return-type]
 }
 ^
cc1: some warnings being treated as errors
source/blender/python/generic/CMakeFiles/bf_python_ext.dir/build.make:185: recipe for target 'source/blender/python/generic/CMakeFiles/bf_python_ext.dir/py_capi_utils.c.o' failed
make[3]: *** [source/blender/python/generic/CMakeFiles/bf_python_ext.dir/py_capi_utils.c.o] Error 1

Once python3.5 is the default python3 this will be a serious bug.

Scott K