[issue20428] _Py_open does not work with O_CREAT
Alexandre Vassalotti
report at bugs.python.org
Wed Jan 29 02:11:17 CET 2014
Alexandre Vassalotti added the comment:
> What is the current behaviour?
I don't think the behaviour is defined. At least, I know it causes recent GCC/glibc combination to throw a compilation error when _FORTIFY_SOURCE is defined:
http://www.eglibc.org/cgi-bin/viewvc.cgi/trunk/libc/io/open_2.c?view=markup
For example, this is the error I got when I tried to compile Python with LTO:
gcc-4.6 -pthread -flto -fuse-linker-plugin -Xlinker -export-dynamic -o python Modules/python.o libpython3.4m.a -lpthread -ldl -lutil -lm
bytesobject.o (symbol from plugin): warning: memset used with constant zero length parameter; this could be due to transposed parameters
In file included from ./Modules/_localemodule.c:404:0,
from :459:
/usr/include/x86_64-linux-gnu/bits/fcntl2.h: In function ‘_Py_open’:
/usr/include/x86_64-linux-gnu/bits/fcntl2.h:51:24: error: call to ‘__open_missing_mode’ declared with attribute error: open with O_CREAT in second argument needs 3 arguments
lto-wrapper: gcc-4.6 returned 1 exit status
/usr/bin/ld: lto-wrapper failed
collect2: ld returned 1 exit status
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20428>
_______________________________________
More information about the Python-bugs-list
mailing list