Building with seccomp

[Hal Murray]

If you are missing a library or header, --enable-seccomp gives a warning but 
doesn't bail.  Should that be changed?

There are 3 seccomp symbols setup in config.h
  #define ENABLE_SECCOMP 1 /* Enable seccomp */
  #define HAVE_SECCOMP_H 1
  #define HAVE_SECCOMP 1

Is there any reason for more then one?  It only builds on Linux.  We need 
both the header and library.


-- 
These are my opinions.  I hate spam.