Building evolution for some reason appears to be doing the equivalent of a make -k/--keep-going i.e. it carries on after errors, only reporting a failure at the end. (This is a pain because a build typically takes up to 45 minutes and I'd like to know immediately when it dies; I turned this on myself when fixing up missing declarations, but I thought I'd turned it off) evolution-2.4.2 is doing this; I think I've seen it with 2.4.1 as well
Would -Wfatal-errors help?
... he wonders to himself since Dave is probably no longer interested.
mbarnes: so are you seeing this behaviour, or was it just me?
Maybe. When building packages I usually just dump the output to a file and sift through it once rpmbuild finally aborts. The error usually appears somewhere in the middle of the file. But I've not seen this when building from GNOME CVS/Subversion. Compilation errors abort immediately, as expected.
I think this might be related to the RPM builds using multiple processors. Compilation on one processor fails but the other ones finish their tasks before noticing the other processor has failed. I don't know, just a guess. In any case, I usually just dump build output to a log file and look at that for errors, so this isn't really getting in my way. Closing as WONTFIX just to get it off my bug list.