Displaying 4 results from an estimated 4 matches for "fcntl2".
Did you mean:
fcntl
2014 May 28
1
Bug#749612: blktap: Conflicting declarations of function __open_2
...90.so -o .libs/libvhdio-2.0.90.so
error: conflicting function declarations "__open_2"
old definition in module libvhdio file libvhdio.c line 992
signed int (const char *pathname, signed int flags, unsigned int _mode)
new definition in module libvhd file /usr/include/x86_64-linux-gnu/bits/fcntl2.h line 26
signed int (const char *, signed int)
Makefile:456: recipe for target 'libvhdio.la' failed
make[6]: *** [libvhdio.la] Error 64
As this implementation of __open_2 appears to require 3 arguments, undefined
behaviour should be expected when called as all public declarations of __ope...
2008 Jul 21
1
1.3.10 compile failure on FC9 w/ Gluster-patched Fuse
...alue of 'asprintf', declared with attribute
warn_unused_result server-protocol.c:5648: warning: ignoring return
value of 'asprintf', declared with attribute warn_unused_result In
function 'open', inlined from 'mop_setspec' at
server-protocol.c:5356: /usr/include/bits/fcntl2.h:51: error: call to
'__open_missing_mode' declared with attribute error: open with O_CREAT
in second argument needs 3 arguments make[5]: *** [server-protocol.o]
Error 1 make[5]: Leaving directory
`/usr/src/redhat/BUILD/glusterfs-1.3.10/xlators/protocol/server/src'
make[4]: *** [all-rec...
2008 Oct 23
4
First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
Hello Dovecot users,
Finally, after little more than a year, I finished the first release of
the new Sieve implementation for Dovecot.
The main reason for rewriting the Sieve engine is to provide more
reliable script execution and to provide better error messages to users
and system administrators. Also, since the Sieve language evolves
quickly, with new language extensions published every
2008 Oct 23
4
First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
Hello Dovecot users,
Finally, after little more than a year, I finished the first release of
the new Sieve implementation for Dovecot.
The main reason for rewriting the Sieve engine is to provide more
reliable script execution and to provide better error messages to users
and system administrators. Also, since the Sieve language evolves
quickly, with new language extensions published every