[bug #30614] Output redirection with &> not parsed correctly in make 3.81 and up

2010-07-31 Thread Joey Adams
Follow-up Comment #1, bug #30614 (project make): Update: The issue turned out to be make using /bin/sh instead of bash. Only the latter supports the &> syntax. ___ Reply to this item at:

[bug #30614] Output redirection with &> not parsed correctly in make 3.81 and up

2010-07-31 Thread Joey Adams
URL: Summary: Output redirection with &> not parsed correctly in make 3.81 and up Project: make Submitted by: joeyalanadams Submitted on: Sun 01 Aug 2010 04:46:57 AM GMT Severity: 3 -

Re: including makefile name and line number for shell_function_completed

2010-07-31 Thread Philip Guenther
On Sat, Jul 31, 2010 at 4:54 PM, Jon Grant wrote: > I am using make 3.81 built for MinGW. > > How easy to output the Makefile.mak:line for each command that fails to start? I don't think there's any way for a snippet of Makefile to figure out what its line # and filename are. The $(warning) func

Re: insufficient debug info from gnu-make

2010-07-31 Thread Philip Guenther
On Sat, Jul 31, 2010 at 7:19 PM, Peter Lawrence wrote: > On Jul 31, 2010, at 9:41 AM, Eli Zaretskii wrote: >>>           one thing I remember in detail about Sun's make, is that >>> instead of writing a level number >>> >>> make[3]: ... >>> make[2]: ... >>> make[1]: ... >>> >>> it wrote out the di

including makefile name and line number for shell_function_completed

2010-07-31 Thread Jon Grant
Hello I am using make 3.81 built for MinGW. How easy to output the Makefile.mak:line for each command that fails to start? I saw this function is what outputs the error, but not sure how to get file and line number info. Any ideas? Thanks, Jon shell_function_completed if (werr

Re: insufficient debug info from gnu-make

2010-07-31 Thread Peter Lawrence
On Jul 31, 2010, at 9:41 AM, Eli Zaretskii wrote: From: Peter Lawrence Date: Sat, 31 Jul 2010 07:41:49 -0700 Cc: bug-make@gnu.org one thing I remember in detail about Sun's make, is that instead of writing a level number make[3]: ... make[2]: ... make[1]: ... it wrote out the dir

Re: insufficient debug info from gnu-make

2010-07-31 Thread Eli Zaretskii
> From: Peter Lawrence > Date: Sat, 31 Jul 2010 07:41:49 -0700 > Cc: bug-make@gnu.org > >one thing I remember in detail about Sun's make, is that > instead of writing a level number > > make[3]: ... > make[2]: ... > make[1]: ... > > it wrote out the directory that the commands had

Re: insufficient debug info from gnu-make

2010-07-31 Thread Peter Lawrence
Paul, one thing I remember in detail about Sun's make, is that instead of writing a level number make[3]: ... make[2]: ... make[1]: ... it wrote out the directory that the commands had cd'ed to before recursing (and maybe the file name, can't be sure any more) make[foo/bar]: ...

[bug #30612] make-3.82 parse error

2010-07-31 Thread Peter Breitenlohner
URL: Summary: make-3.82 parse error Project: make Submitted by: breitenlohner Submitted on: Sat 31 Jul 2010 02:20:49 PM GMT Severity: 3 - Normal Item Group: None