Re: Infinite loop bug with parallel make

2013-02-23 Thread Paul Smith
On Sat, 2013-02-23 at 21:02 +, Ian Lynagh wrote: > On Sat, Feb 23, 2013 at 03:45:59PM -0500, Paul Smith wrote: > > > > I've never really been clear on the purpose and use of .SECONDARY; the > > comments in both the GNU make manual and in the code seem odd to me. I > > would really appreciate

Re: Infinite loop bug with parallel make

2013-02-23 Thread Ian Lynagh
On Sat, Feb 23, 2013 at 03:45:59PM -0500, Paul Smith wrote: > > I've never really been clear on the purpose and use of .SECONDARY; the > comments in both the GNU make manual and in the code seem odd to me. I > would really appreciate anyone out there who is using this (either for > specific targe

Re: Infinite loop bug with parallel make

2013-02-23 Thread Paul Smith
On Sat, 2013-02-23 at 17:28 +, Ian Lynagh wrote: > On Sat, Feb 23, 2013 at 06:57:27AM +0200, Shachar Shemesh wrote: > > > > What I'm also interested in is why .SECONDARY made everything slow. > > I've put a cut-down makefile demonstrating this here: > http://urchin.earth.li/~ian/tmp/Makef

Re: Infinite loop bug with parallel make

2013-02-23 Thread Ian Lynagh
Hi Shachar, On Sat, Feb 23, 2013 at 06:57:27AM +0200, Shachar Shemesh wrote: > > What I'm also interested in is why .SECONDARY made everything slow. I've put a cut-down makefile demonstrating this here: http://urchin.earth.li/~ian/tmp/Makefile First run $ make setup (which creates some

Re: Infinite loop bug with parallel make

2013-02-23 Thread Ian Lynagh
On Sat, Feb 23, 2013 at 01:50:38PM +, Ian Lynagh wrote: > On Fri, Feb 22, 2013 at 09:38:22PM -0500, Paul Smith wrote: > > On Sat, 2013-02-23 at 02:32 +, Ian Lynagh wrote: > > > The problem was that our compiler generates 2 output files (foo.o and > > > foo.hi) when compiling one source file

Re: Infinite loop bug with parallel make

2013-02-23 Thread Ian Lynagh
On Fri, Feb 22, 2013 at 09:38:22PM -0500, Paul Smith wrote: > On Sat, 2013-02-23 at 02:32 +, Ian Lynagh wrote: > > The problem was that our compiler generates 2 output files (foo.o and > > foo.hi) when compiling one source file, and we had thus ended up with > > a bunch of rules like > > %.