Marc-Andre Lemburg <m...@egenix.com> added the comment: STINNER Victor wrote: > > STINNER Victor <victor.stin...@haypocalc.com> added the comment: > >> (or to fix it, but that's a major task - the whole CFLAGS >> and LDFLAGS system used in Python's configure has over the >> years turned into a complete mess). > > What do you mean by "a complete mess"?
There's a discussion on some other ticket about this. Basically, Python's configure script doesn't really allow setting CFLAGS in a meaningful way via env vars (which it should to be standards conform). It adds all sorts of non-standard variables which are then combined to build the final CFLAGS variable: BASECFLAGS, EXTRA_CFLAGS and OPT. > Did you try my patch? Is it enough to fix this issue? No. It doesn't allow overriding the CFLAGS settings actually used by the system. You'd also need to set BASECFLAGS="", OPT="" and EXTRA_CFLAGS="" in addition to applying your patch and setting CFLAGS to "-O0". > A least, my patch is enough to disable all compilation optimization if > --with-pydebug option is used (which was my first goal). It unconditionally overrides CFLAGS - even if it is not set and defined by AC_PROG_CC as "-g -O2". That would need to be corrected. Other than that it does help a little work around the mess :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8211> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com