Re: Problems with latest Cygwin make patch; builds OK but binary segfaults

2006-08-25 Thread Eli Zaretskii
> From: "William Sheehan" <[EMAIL PROTECTED]> > Date: Fri, 25 Aug 2006 10:52:00 -0700 > > > Please rune "make check" on the version of Make you think > > fixes the problem. If all the tests pass, please post here a > > patch that you used to fix the recursion problem. Thanks. > > Done; the pa

RE: Problems with latest Cygwin make patch; builds OK but binary segfaults

2006-08-25 Thread William Sheehan
> The patch is really not mine, Eli, myself and Chris came up > with it. And now you. :) > > Thanks for finding the problem. I stand corrected; thanks to all involved! William Sheehan Builds Engineer / Network Administrator Open Interface North America _

RE: Problems with latest Cygwin make patch; builds OK but binary segfaults

2006-08-25 Thread William A. Hoffman
At 01:52 PM 8/25/2006, William Sheehan wrote: >> Please rune "make check" on the version of Make you think >> fixes the problem. If all the tests pass, please post here a >> patch that you used to fix the recursion problem. Thanks. > >Done; the patch is attached. Running make check came back w

RE: Problems with latest Cygwin make patch; builds OK but binary segfaults

2006-08-25 Thread William Sheehan
> Please rune "make check" on the version of Make you think > fixes the problem. If all the tests pass, please post here a > patch that you used to fix the recursion problem. Thanks. Done; the patch is attached. Running make check came back with zero failures and a nice smiley face. The patc

Re: Problems with latest Cygwin make patch; builds OK but binary segfaults

2006-08-25 Thread Eli Zaretskii
> From: "William Sheehan" <[EMAIL PROTECTED]> > Date: Fri, 25 Aug 2006 00:57:35 -0700 > > The basic cause of the problems are the ~ and ! characters defined in > sh_chars, line 2304 of job.c in the untouched make 3.81 sources. Or rather, > that a Cygwin build uses sh_chars when (I think) it shoul

RE: Problems with latest Cygwin make patch; builds OK but binary segfaults

2006-08-25 Thread William Sheehan
> It could be an infinite recursion in > construct_command_argv_internal, but it could also be > something else. First, is it reasonable to get a stack > overflow in a Cygwin program after only 11 recursive > invocations of construct_command_argv_internal? Can you > verify directly that the