[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Sqlite compiler spam delenda est.

From: Gabriela Gibson <gabriela.gibson_at_gmail.com>
Date: Tue, 01 Oct 2013 00:28:03 +0100

Because sqlite produces ~50000 extra letters of bumpf per compile that
often obscures actually important compiler messages, I've not been as
diligent as I should have been about reading compiler messages. A lot
the time I get lucky and it doesn't matter, but I also got caught out by

Here is how to get rid of all the noise and make your compiler output
useful once again:

First we take a snapshot of the 'native' compiler messages that come
with the trunk:

make 1>stdout.report 2>stderr.constant; \
sort --unique stderr.constant > stderr.unique | grep -v sqlite

This removes the sqlite warnings and shows you only the current warning
messages that are actually ~/trunk related.

Any subsequent compiles that are started with the line below will use
the generated stderr.unique file to filter output and remove every
compiler message that is 'native' to the trunk, leaving just the
messages that pertain to your code:

make > stdout.report 2> >(tee stderr.report | while read line; do echo
$line | grep -F -- $line" stderr.unique 2> /dev/null; if [ $? = 1 ];
then echo "$line" >&2; fi; done)

You can also type this line when you invoke the emacs compile buffer and
your C-x ` will continue to work.
Received on 2013-10-01 01:27:42 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.