I generally agree that logging is something I want to tune dynamically. Logging is one of the few things I prefer as an environment variable.
As a compromise though perhaps a configure option to adjust the default logging level might work. Still overridable via LOG but with a configurable default. The help documentation could/should also be improved to document "Environment variables which can effect configuration" and "Environment variables which can effect build". These do need to be described separately even if there are some which apply to both. Mike On Mar 13 2013, at 12:06 , Dalibor Topic wrote: > On 3/13/13 7:35 PM, Andrew Hughes wrote: >> I still think it should be a configure option, which is the first place I >> looked. > > You'd usually use it if something interesting happens, like a build failure, > and > it's a you're 'not sure how it could have come to this' situation, so in that > case, > having to re-run configure, and potentially the whole build again seems like > a worse > option then just adding a variable to the make run as you need it (or not). > > cheers, > dalibor topic > > -- > Oracle <http://www.oracle.com> > Dalibor Topic | Principal Product Manager > Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961 > <tel:+491737185961> > Oracle Java Platform Group > > ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg > > ORACLE Deutschland B.V. & Co. KG > Hauptverwaltung: Riesstr. 25, D-80992 München > Registergericht: Amtsgericht München, HRA 95603 > Geschäftsführer: Jürgen Kunz > > Komplementärin: ORACLE Deutschland Verwaltung B.V. > Hertogswetering 163/167, 3543 AS Utrecht, Niederlande > Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 > Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher > > Green Oracle <http://www.oracle.com/commitment> Oracle is committed to > developing practices and products that help protect the environment
