Re: [bug #40225] Deterministic output ordering

2013-10-11 Thread Tim Murphy
The idea of diffing 2 builds is truly a cool one - especially when they're huge - but I'd rather it was done according to keys or other factors e.g. target name. I'd like to compare the time it took to build various targets and find out why a target took so much longer in the new build. I'd

Re: [bug #40225] Deterministic output ordering

2013-10-11 Thread Edward Welbourne
Then commit all the log files to git and use git show to find out which of them have changed since the last build. (I trust you can all work out the equivalent steps for *your* preferred SCM system.) This only has to happen on the server that builds from clean on a regular basis. Or just

[bug #33034] Makefile:23: *** mixed implicit and normal rules. Stop. for Linux kernel out of source builds

2013-10-11 Thread David Boyce
Follow-up Comment #12, bug #33034 (project make): I'm uploading a patch that adds an --allow-mixed-rules option which converts the fatal error to a warning. This is the only testing it's been subjected to: % cat Makefile all %.o: @echo Making $@ % make-4.0 Makefile:1: *** mixed implicit

[bug #33034] Makefile:23: *** mixed implicit and normal rules. Stop. for Linux kernel out of source builds

2013-10-11 Thread David Boyce
Follow-up Comment #14, bug #33034 (project make): Yes, I realize it's a bit of a wing and a prayer but from the git log it looks like this fix got into the same commit as a rewrite of major sections of read.c. Without reading and thinking through all of it, I figured there was a chance that