François Pinard wrote:
[Andreas Jaeger]
Yes, your hope [of "warning-clean" include files] is reasonable - and as glibc developers we strive to fix this but depend on external programs - and not always compile with all possible flags.
I usually try to preset `CFLAGS' to many warnings in the environment at `login' time, and the `CFLAGS' value then gets configured into `config.status' rather automatically. I would not recommend to do this because this can interfere with CFLAGS settings in many configuration scripts. Imagine to have -mcpu=pentium in a CFLAGS environment and then try to cross-compile a library.
Instead, if you think you need to override CFLAGS, CPPFLAGS etc., better pass them from the command line at configuration time (Should works with properly written autoconf/automake configurations), eg.: CFLAGS=-Wall CPPFLAGS=-DFOO=foo ./configure This essentially is the same as setting them as environment variables, but requires one additional stage of thought, therefore is less error-prone and spares you being hit by invalid CFLAGS settings months later, when you don't recall anymore having set them in the environment. OTOH, you should normally trust in the settings a packages' maintainers think are suiteable. In general they know better than you - but nobody is perfect :) Ralf -- Ralf Corsepius Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung (FAW) Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690 mailto:corsepiu@faw.uni-ulm.de FAX: +49/731/501-999 http://www.faw.uni-ulm.de -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/