Let me add my voice as a user. If you are one of the lucky people whose
builds consist mostly of 1 line of output per rule then you will rarely
have any trouble in a good build but try interpreting error messages from
compiler/tool X when they're 10 lines from the file that they refer to and
Date: Mon, 29 Apr 2013 09:58:50 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: bug-make@gnu.org bug-make@gnu.org
try interpreting error messages from compiler/tool X when they're 10
lines from the file that they refer to and don't include the
filename in the error message.
That's
On 29 April 2013 16:19, Eli Zaretskii e...@gnu.org wrote:
Date: Mon, 29 Apr 2013 09:58:50 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: bug-make@gnu.org bug-make@gnu.org
try interpreting error messages from compiler/tool X when they're 10
lines from the file that they refer to and
Date: Mon, 29 Apr 2013 16:40:03 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: bug-make@gnu.org bug-make@gnu.org
cc fred.c -c -o fred.o
cc bob.c -c -o bob.o
error on line 20 -X
Which one?
Make will actually tell you which one, something like:
makefile:342: recipe for target
On Mon, Apr 29, 2013 at 10:30 AM, Tim Murphy tnmur...@gmail.com wrote:
cc fred.c -c -o fred.o
cc bob.c -c -o bob.o
error on line 20 -X
error on line 30 -
error on line 330 -
makefile:342: recipe for target 'fred.o' failed
makefile:350: recipe for target 'bob.o' failed
?
Come now - the broken excuse is an excuse. There's plenty of crap free
software out there and some poor bastard trying to build it who can't
change the source because the people who own it think it should be make's
problem.
:-)
Cheers,
Tim
On 29 April 2013 19:00, Philip Guenther
Date: Mon, 29 Apr 2013 18:30:37 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: bug-make@gnu.org bug-make@gnu.org
cc fred.c -c -o fred.o
cc bob.c -c -o bob.o
error on line 20 -X
error on line 30 -
error on line 330 -
makefile:342: recipe for target 'fred.o' failed
Date: Mon, 29 Apr 2013 19:33:10 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: Eli Zaretskii e...@gnu.org, bug-make@gnu.org bug-make@gnu.org
Come now - the broken excuse is an excuse. There's plenty of crap free
software out there and some poor bastard trying to build it who can't
change
One doesn't have to suffer the problems and learn the option exists
afterwards.
In the end I can understand why a new feature might not be default to start
with - until a lot of people have used it and are sure that it works
everywhere.
Cheers,
Tim
On 29 April 2013 20:21, Eli Zaretskii
Eli:
cc fred.c -c -o fred.o
cc bob.c -c -o bob.o
error on line 20 -X
error on line 30 -
error on line 330 -
makefile:342: recipe for target 'fred.o' failed
makefile:350: recipe for target 'bob.o' failed
You need to look in both anyway.
That is true of the very specific
Now that we seem to have a workable solution for output synchronization
for both POSIX and Windows systems, I wonder if we shouldn't consider
enabling it as the default mode when parallel builds are running.
I understand that this will be a change that could be visible (beyond
the collection of
From: Paul Smith psm...@gnu.org
Cc: bug-make@gnu.org
Date: Sun, 28 Apr 2013 22:03:39 -0400
Now that we seem to have a workable solution for output synchronization
for both POSIX and Windows systems, I wonder if we shouldn't consider
enabling it as the default mode when parallel builds are
12 matches
Mail list logo
