* Tomasz Rybak <[email protected]>, 2012-05-24, 22:13:
W: python-pyopencl: hardening-no-fortify-functions usr/lib/python2.6/dist-packages/pyopencl/_cl.so W: python-pyopencl: hardening-no-stackprotector usr/lib/python2.6/dist-packages/pyopencl/_pvt_struct.so
hardening-no-fortify-functions and hardening-no-stackprotector are prone to false-positives. There's a bug report in the BTS about this.
Sample gcc call: gcc -pthread -fwrapv -Wall -O3 -DNDEBUG -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPYGPU_PACKAGE=pyopencl -DPYGPU_PYOPENCL=1 -DPYOPENCL_USE_DEVICE_FISSION=1 -DHAVE_GL=1 -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.2mu -c src/wrapper/wrap_cl_part_2.cpp -o build/temp.linux-x86_64-3.2/src/wrapper/wrap_cl_part_2.o so hardening options are given to the compiler.
That's for Python 3.2. What about Python 2.6? -- Jakub Wilk -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
