Remove AC_FUNC_SETPGRP as it can cause issues when cross-compiling

I considered only skipping it when cross-compiling, but given
that Privoxy doesn't use setpgrp(2), why should we care about
its prototype?

There's no justification for the check in the revision log
either, except that it was part of "Al's patch".

diff --git a/configure.in b/configure.in
index b406a89..6ec2d74 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -1,6 +1,6 @@
 dnl Process this file with autoconf to produce a configure script.
 dnl 
-dnl $Id: configure.in,v 1.152 2011/04/19 11:42:51 fabiankeil Exp $
+dnl $Id: configure.in,v 1.153 2011/04/19 13:00:47 fabiankeil Exp $
 dnl 
 dnl Written by and Copyright (C) 2001-2010 the
 dnl Privoxy team. http://www.privoxy.org/
@@ -32,7 +32,7 @@ dnl =================================================================
 dnl AutoConf Initialization
 dnl =================================================================
 
-AC_REVISION($Revision: 1.152 $)
+AC_REVISION($Revision: 1.153 $)
 AC_INIT(jcc.c)
 
 if test ! -f config.h.in; then
@@ -707,7 +707,6 @@ AC_CHECK_FUNCS([strerror bcopy memmove])
 AC_PROG_GCC_TRADITIONAL
 dnl uncommenting does not work for swa. suse linux
 dnl AC_FUNC_MALLOC
-AC_FUNC_SETPGRP
 AC_TYPE_SIGNAL
 dnl uncommenting does not work for swa. suse linux
 dnl AC_FUNC_STAT