Why is CFLAGS in Makefile.pre.in specified as CFLAGS= $(BASECFLAGS) $(OPT) $(EXTRA_CFLAGS) whereas that will negate any CFLAGS you pass to configure?
A normal call to configure (as ./configure --help also explains) can contain a CFLAGS specification, e.g.: CFLAGS="-compiler_options" ./configure --config_options Configure happily compiles and tests everything with the working CFLAGS (as evident in config.log), but when it comes to the output substitution it will, of course, not be overridden. Now, I realize that configure.in talks about BASECFLAGS and OPT, but neither of these are documented in the ./configure --help output, nor are they standard when it comes to autotooling. Passing CFLAGS is the defacto standard. Furthermore, when passing compiler options to OPT, these are NOT taken along in the configure tests, which means you might have passed faulty options but configure will not detect any problems with them. You will only encounter this when you start building. So is there any rationale for all this? -- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ Contentment that derives from knowing when to be content is eternal contentment... _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
