This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: SETPGRP and autoconf
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: SETPGRP and autoconf
- From: Daniel Jacobowitz <dmj+ at andrew dot cmu dot edu>
- Date: Fri, 27 Jul 2001 13:41:07 -0700
- Cc: Mark Kettenis <kettenis at wins dot uva dot nl>, gdb-patches at sources dot redhat dot com
- References: <20010725162420.A13860@nevyn.them.org> <200107261040.f6QAe2T05377@delius.kettenis.local> <20010726084450.A2941@nevyn.them.org> <3B60505D.5080304@cygnus.com> <20010727102017.A5627@nevyn.them.org> <3B61CFB7.9080302@cygnus.com>
On Fri, Jul 27, 2001 at 04:31:51PM -0400, Andrew Cagney wrote:
> > +dnl AC_FUNC_SETPGRP does not work if cross compiling
> > +dnl Instead, assume we will have a prototype for setpgrp if cross compiling.
> > +if test "$cross_compiling" = no; then
>
>
> Suggest:
> AC_FUNC_SETPGRP does not work when cross compiling GDB.
>
> BTW, I suspect the outcome of the test on modern OS's doesn't matter -
> the better defined setpgid() is used first anyway.
Hey, I missed this when going over the logic. We don't even care about
SETPGRP_VOID if HAVE_SETPGID. I'm still going to check it this way,
though, just in case we have a system modern enough to have the headers
and odd enough not to define setpgid.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer