Comment 2 for bug 1691658

Ok, the gcc error seems to be "normal"?
Maybe it just went undetected so far.

The good build has this as well:
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c ovs/_json.c -o build/temp.linux-x86_64-2.7/ovs/_json.o
ovs/_json.c:1:20: fatal error: Python.h: No such file or directory
 #include "Python.h"
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.5m -c ovs/_json.c -o build/temp.linux-x86_64-3.5/ovs/_json.o
ovs/_json.c:1:20: fatal error: Python.h: No such file or directory
 #include "Python.h"

Once per python version, the openvswitch build automatically does:
WARNING: The C extension could not be compiled, speedups are not enabled.
Failure information, if any, is above.
Retrying the build without the C extension.

Need to discuss if that is ok or another issue in itself, but that means the FTBFS atm is only about:
GOOD
running install_scripts
install -D _dpdk/vswitchd/ovs-vswitchd \
        /<<PKGBUILDDIR>>/debian/openvswitch-switch-dpdk/usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk

BAD
running install_scripts
/bin/sh: 2: cd: can't cd to python
debian/rules:84: recipe for target 'override_dh_install' failed