Re: seccomp selftest fails to build with glibc 2.26

2017-09-07 Thread Kees Cook
On Thu, Sep 7, 2017 at 2:27 PM, Seth Forshee wrote: > Hi Kees, > > I'm seeing build failures with your seccomp selftest when using glibc > 2.26. The first are related to changing macro names from __have_sig*_t > to __sig*_t_defined. But after defining those there are more conflicting > definitions

seccomp selftest fails to build with glibc 2.26

2017-09-07 Thread Seth Forshee
Hi Kees, I'm seeing build failures with your seccomp selftest when using glibc 2.26. The first are related to changing macro names from __have_sig*_t to __sig*_t_defined. But after defining those there are more conflicting definitions. I was able to get it to build with the changes below, however