Re: patch to autoconfiscate vfork handling

["Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>]

 > From: Jeffrey A Law <law@cygnus.com>
 > 
 >   In message <199810301531.KAA17171@caip.rutgers.edu>you write:
 >   > 	This patch adds autoconf support for vfork instead of checking
 >   > macro USG.  I included changes to the gcc dir (for collect2.c) as well
 >   > as a libiberty dir change (for pexecute.c) in this one file since they
 >   > go together and were relatively small.
 >   > 
 >   > 
 >   > 	The libiberty/pexecute.c changes didn't require using
 >   > AC_FUNC_VFORK since libiberty/configure.in already calls it. 
 >   > 
 >   > 	Okay to install?
 > 
 > They look fine to me.


	Thanks, installed.


 > At first I thought we had potential canadian cross problems, but then I 
 > remembered that pexecute.c is built for the host, not the build machine
 > within the gcc dir itself.
 > jeff


	Is the fact that we build pexecute.c within the gcc dir itself
crucial?

	What about when we stop building it in the gcc dir and get it
straight from libiberty?

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Icon CMT Corp.