From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb@sources.redhat.com, Mark Kettenis <kettenis@science.uva.nl>
Subject: SETPGRP and autoconf
Date: Wed, 25 Jul 2001 16:24:00 -0000
Message-id: <20010725162420.A13860@nevyn.them.org>
X-SW-Source: 2001-07/msg00365.html

I should have objected :)  But it'd been so long since I last saw this issue
that I forgot about it.

AC_FUNC_SETPGRP has some regrettable problems.  Witness:

checking whether setpgrp takes no argument... configure: error: cannot check
  setpgrp if cross compiling

Thus breaking all host-x-host cross builds.


This is what I really hate about autoconf.  There's no good reason for
AC_FUNC_SETPGRP to be an executed test.  If you have a prototype for
setpgrp(void),  setpgrp(1,1) won't compile, and you don't need to execute
anything at all.

What can we do about this?  Besides my usual hack: I have a huge list of
autoconf cache variables in my build environment, preset.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer