search for: sigev

Hello all, We migrated recently from AIX5.0 to AIX 5.2. I am getting the following warnings/errors during compilation: The following are some: /usr/include/time.h:236: warning: `struct sigevent' declared inside parameter list /usr/include/time.h:236: warning: its scope is only this definition or declaration, which is probably not what you want. /usr/include/time.h:236: warning: `struct sigevent' declared inside parameter list /usr/include/time.h:236: warning: its scope is only...

.../usr/include/sys/audit.h:284: warning: `\' followed by white space at end of line /usr/include/sys/audit.h:287: warning: `\' followed by white space at end of line In file included from ../includes.h:34, from bsd-arc4random.c:25: /usr/include/time.h:230: warning: `struct sigevent' declared inside parameter list /usr/include/time.h:230: warning: its scope is only this definition or declaration, which is probably not what you want. In file included from ../openbsd-compat/port-aix.h:34, from ../openbsd-compat/openbsd-compat.h:166, from...

https://bugzilla.mindrot.org/show_bug.cgi?id=3085 Bug ID: 3085 Summary: seccomp issue after upgrading openssl Product: Portable OpenSSH Version: 8.1p1 Hardware: Other OS: Linux Status: NEW Severity: critical Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org

...or ssize_t... (cached) yes checking for wchar_t... yes checking for cups-config... no checking if the compiler will optimize out function calls... yes checking for fd passing via msg_control... no checking for fd passing via msg_acctrights... no checking for dirfd... (cached) no checking for struct sigevent type... yes checking for struct sigevent.sigev_value.sival_ptr... yes checking for struct sigevent.sigev_value.sigval_ptr... no checking for struct timespec type... yes checking for real setresuid... no checking for real setresgid... no checking for working memcmp... (cached) yes checking whethe...

...r ssize_t... (cached) yes checking for wchar_t... yes checking for cups-config... no checking if the compiler will optimize out function calls... yes checking for fd passing via msg_control... yes checking for fd passing via msg_acctrights... no checking for dirfd... (cached) no checking for struct sigevent type... yes checking for struct sigevent.sigev_value.sival_ptr... yes checking for struct sigevent.sigev_value.sigval_ptr... no checking for struct timespec type... yes checking for real setresuid... no checking for real setresgid... no checking for working memcmp... (cached) yes checking whethe...

...Checking whether sysconf(_SC_PAGESIZE) is available : yes Checking whether to use the Darwin-specific initgroups system call : no Checking whether struct utimbuf is available : yes Checking whether we have the struct sigevent : yes Checking for member sigev_value.sival_ptr in struct sigevent : yes Checking for member sigev_value.sigval_ptr in struct sigevent : no Checking for the maximum value of the 'time_t' type...

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *

...ssize_t... (cached) yes checking for wchar_t... yes checking for cups-config... no checking if the compiler will optimize out function calls... yes checking for fd passing via msg_control... yes checking for fd passing via msg_acctrights... no checking for dirfd... (cached) yes checking for struct sigevent type... yes checking for struct sigevent.sigev_value.sival_ptr... yes checking for struct sigevent.sigev_value.sigval_ptr... no checking for real setresuid... yes checking for real setresgid... yes checking for working memcmp... (cached) yes checking whether to use readline... yes checking readl...

I've mentioned this topic before (in fact, the idea of adding NBD_CMD_FLAG_DF was first mentioned at [1]), but finally finished enough of an implementation to feel confident in posting it. I'd still like to add something under examples/ that uses the new API to implement strict checking of a server's structured replies read implementation (ensure that a server never sends data after