Update of bug #42910 (project make):
Status:None = Works for me
Open/Closed:Open = Closed
___
Follow-up Comment #1:
Hi Manoj; I ran the
Follow-up Comment #5, bug #42390 (project make):
There is already a way to choose a longer timeout: the run_make_test() method
takes an optional extra argument which is the timeout value.
I increased this to 300; hopefully that will solve this problem (I cannot
reproduce the original problem on
Follow-up Comment #1, bug #43936 (project make):
putchar and puts are not handled purposefully: at the very end when make exits
it will verify that there is no error with stdout. See the close_stdout()
function in output.c file and the long comment before that: this is a
standard method of
Update of bug #45486 (project make):
Status:None = Not A Bug
Open/Closed:Open = Closed
___
Follow-up Comment #2:
I'm going to close this
Follow-up Comment #1, bug #43363 (project make):
It's fantastic that you've provided reproducible cases (although please attach
the sample files directly to the bug in the future rather than using
pastebin).
However for errors this complex it would be really, really helpful if for each
example
Update of bug #43921 (project make):
Status:None = Duplicate
Open/Closed:Open = Closed
___
Follow-up Comment #1:
This was fixed
Update of bug #43689 (project make):
Status:None = Duplicate
Open/Closed:Open = Closed
___
Follow-up Comment #4:
No reply so closed as a
Update of bug #28092 (project make):
Status:None = Fixed
Assigned to:None = psmith
Open/Closed:Open = Closed
Fixed Release:
Update of bug #43936 (project make):
Status:None = Fixed
Assigned to:None = psmith
Open/Closed:Open = Closed
Fixed Release:
Update of bug #45275 (project make):
Status:None = Fixed
Assigned to:None = psmith
Open/Closed:Open = Closed
Fixed Release:
Update of bug #45050 (project make):
Status:None = Fixed
Assigned to:None = psmith
Open/Closed:Open = Closed
Component Version:
Update of bug #45049 (project make):
Status:None = Fixed
Assigned to:None = psmith
Open/Closed:Open = Closed
Component Version:
Update of bug #43757 (project make):
Item Group: Bug = Enhancement
___
Follow-up Comment #1:
The problem is this; the GNU make manual says: a file cannot be intermediate
if it is mentioned in
Follow-up Comment #2, bug #43936 (project make):
Would it be a bit safer to detect every error situation as early as possible?
When does a failed output need an immediate reaction in this software?
___
Reply to this item at:
Update of bug #43677 (project make):
Status:None = Fixed
Assigned to:None = psmith
Open/Closed:Open = Closed
Fixed Release:
Update of bug #41813 (project make):
Status:None = Fixed
Assigned to:None = psmith
Open/Closed:Open = Closed
Fixed Release:
Follow-up Comment #3, bug #43936 (project make):
I don't see any point in detecting errors writing to stdout as early as
possible. If you can think of one please mention it.
___
Reply to this item at:
Very long symbolic links could completely fill the buffer. Adding a
terminating '\0' later on would overflow it by one byte.
---
remake.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/remake.c b/remake.c
index 0888cff..854c42b 100644
--- a/remake.c
+++ b/remake.c
@@ -1520,7
Update of bug #44660 (project make):
Status:None = Duplicate
Open/Closed:Open = Closed
___
Follow-up Comment #3:
Thanks, this is the
Update of bug #44783 (project make):
Status:None = Not A Bug
Open/Closed:Open = Closed
___
Follow-up Comment #1:
It's perfectly
20 matches
Mail list logo