[issue969718] BASECFLAGS are not passed to module build line

STINNER Victor added the comment: This issue has been fixed by bpo-36235. -- nosy: +vstinner resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> distutils.sysconfig.customize_compiler() overrides CFLAGS var with OPT var if CFLAGS env var is

[issue969718] BASECFLAGS are not passed to module build line

Changes by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue969718] BASECFLAGS are not passed to module build line

Ned Deily added the comment: Arfrever, your proposal is certainly one of many possible solutions and one that would be appropriate if we were designing the Python configure, Makefile, and Distutils components from scratch or looking at major changes to Distutils. But we're not at this point.

[issue969718] BASECFLAGS are not passed to module build line

Arfrever Frehtes Taifersar Arahesis added the comment: OPT should not be used in Distutils at all. Lib/distutils/sysconfig.py should have: if 'CFLAGS' in os.environ: cflags = os.environ['CFLAGS'] Makefile.pre.in should have: $(RUNSHARED) CC='$(CC)' LDSHARED='$(BLDSHARED)' CFLAGS

[issue969718] BASECFLAGS are not passed to module build line

Changes by koobs : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mai

[issue969718] BASECFLAGS are not passed to module build line

Ned Deily added the comment: Since I just noticed this and haven't seen it mentioned already: for the record, the Python Makefile for current versions is affected by this issue. The "sharedmods" target, which calls setup.py to build the standard library shared modules, explicitly passes into

[issue969718] BASECFLAGS are not passed to module build line

Changes by Brett Cannon : -- nosy: -brett.cannon versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list maili

[issue969718] BASECFLAGS are not passed to module build line

Antoine Pitrou added the comment: > Any interest in a cleaned up version of the Debian patch (remove > double opt, line length, add documentation for overriding BASECFLAGS > and OPT)? I think it would be nice, but it should have a test if possible. Otherwise there'll keep being regressions. --

[issue969718] BASECFLAGS are not passed to module build line

Chris Lambacher added the comment: Antoine said: > I don't understand how you can cross-compile using the host Python > Makefile. Could you explain? The get_config_vars() function parses the host Makefile to get the values that we are discussing overriding. > EXTRA_CFLAGS is not defined in th

[issue969718] BASECFLAGS are not passed to module build line

Stefan Krah added the comment: Chris Lambacher wrote: > I was cross-compiling to a target architecture that does not support > the -march option so I would not be able to provide a different one > as override. Just out of curiosity: You are cross-compiling a C-extension? How can you be sure t

[issue969718] BASECFLAGS are not passed to module build line

Antoine Pitrou added the comment: > I am not convinced that the minimal patch would work for my original > issue. I wanted to be able to override the -march option which shows > up in OPT on Fedora. I was cross-compiling to a target architecture > that does not support the -march option so I wou

[issue969718] BASECFLAGS are not passed to module build line

Chris Lambacher added the comment: I am not convinced that the minimal patch would work for my original issue. I wanted to be able to override the -march option which shows up in OPT on Fedora. I was cross-compiling to a target architecture that does not support the -march option so I would n

[issue969718] BASECFLAGS are not passed to module build line

Stefan Krah added the comment: EXTRA_CFLAGS were removed in r38848. Is it necessary to configure OPT, BASECFLAGS and EXTRA_CFLAGS via the environment? I think it might be sufficient to take CFLAGS from the Makefile and append the environment CFLAGS. Chris, would the new minimal patch solve you

[issue969718] BASECFLAGS are not passed to module build line

Stefan Krah added the comment: Antoine Pitrou wrote: > Why is OPT duplicated in get_config_vars(...)? I missed that, thanks. > Why do OPT and BASECFLAGS environ vars override their Makefile values > instead of accumulating with them? I think it would go too far to append in three places. If

[issue969718] BASECFLAGS are not passed to module build line

Antoine Pitrou added the comment: Why is OPT duplicated in get_config_vars(...)? Why do OPT and BASECFLAGS environ vars override their Makefile values instead of accumulating with them? Why is EXTRA_CFLAGS not configurable through environ? -- ___ Py

[issue969718] BASECFLAGS are not passed to module build line

Stefan Krah added the comment: Éric, the Debian patch looks good to me and it solves my build problem. The only question I have is why EXTRA_CFLAGS still go behind CFLAGS and cannot be overridden via the environment. But as it is, the patch is an improvement. I'm attaching the version for 2.7.

[issue969718] BASECFLAGS are not passed to module build line

Éric Araujo added the comment: Duplicate report from Stephan Krah: When CFLAGS are set, distutils drops -fno-strict-aliasing (among other flags): $ python2.7 setup.py build ... gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I./src -I/usr/loc

[issue969718] BASECFLAGS are not passed to module build line

Éric Araujo added the comment: Pythons in Debian seem to be immune to this problem, thanks to this patch: http://deb.li/3ku1g (via http://lists.debian.org/debian-python/2010/12/msg5.html). I haven’t had time to learn the intricacies of make variables yet, so I can’t approve a patch. I’m

[issue969718] BASECFLAGS are not passed to module build line

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue969718] BASECFLAGS are not passed to module build line

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue969718] BASECFLAGS are not passed to module build line

Chris Lambacher added the comment: I am attaching a preliminary patch to allow override of $(OPT). I am not sure this is sufficient, but am wary of breaking packages that depend on the existing behaviour. The logic indeed seems wrong, but maybe this is something that has to go in distutils2

[issue969718] BASECFLAGS are not passed to module build line

Changes by Éric Araujo : -- assignee: -> tarek components: +Distutils2 nosy: +eric.araujo versions: +3rd party, Python 3.2 -Python 2.6, Python 3.0 ___ Python tracker ___ __

[issue969718] BASECFLAGS are not passed to module build line

Chris Lambacher added the comment: I am running into a problem related to this. I am attempting to cross compile extensions but Fedora includes -march in the OPT variable. Since there is no way to exclude the OPT values the build fails. It seems that forcing OPT to stay the same is a disservice

[issue969718] BASECFLAGS are not passed to module build line

Changes by Roumen Petrov : -- nosy: +rpetrov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue969718] BASECFLAGS are not passed to module build line

Changes by Akira Kitada : -- nosy: +tarek type: -> behavior versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.4 ___ Python tracker ___ ___