[issue17679] sysconfig generation uses some env variables multiple times

2019-05-17 Thread STINNER Victor
STINNER Victor added the comment: The patch is wrong. I'm not sure when/how C flags are duplicated. Anyway, it seems like the issue is somehow outdated or even gone, so I close the issue. -- resolution: -> out of date stage: patch review -> resolved status: open -> closed __

[issue17679] sysconfig generation uses some env variables multiple times

2018-12-18 Thread STINNER Victor
STINNER Victor added the comment: build.diff: Difference without/with the patch on Python build from source. Example: - CPPFLAGS = "-I. -I./Include" + CPPFLAGS = "-I. -I/Include" This change is wrong: /Include directory doesn't exist. Another example: - LIBPL = "/usr/loca

[issue17679] sysconfig generation uses some env variables multiple times

2018-12-18 Thread STINNER Victor
STINNER Victor added the comment: I don't think that the attached patch is correct. See attached install.diff: difference without/with 00178-dont-duplicate-flags-in-sysconfig.patch on Python installed in /usr/bin/python3. Example of bug: 'TESTRUNNER': 'LD_LIBRARY_PATH=/builddir/build/BUI

[issue17679] sysconfig generation uses some env variables multiple times

2014-12-11 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: The patch doesn't look good to me. If the value contains "-lfoo-lbar $(name)" then substituting name="-lfoo" or name="-lbar" doesn't work. -- nosy: +serhiy.storchaka ___ Python tracker

[issue17679] sysconfig generation uses some env variables multiple times

2014-12-11 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- stage: needs patch -> patch review versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ ___ Pytho

[issue17679] sysconfig generation uses some env variables multiple times

2014-05-25 Thread Florent Rougon
Changes by Florent Rougon : -- nosy: +frougon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue17679] sysconfig generation uses some env variables multiple times

2014-04-26 Thread Christopher Arndt
Christopher Arndt added the comment: Another solution may be to make the test more relaxed and regard the value returned by sysconfig.get_config_var() as a _set_ of shell tokens, whose elements may occur more than once, e.g. def test_sysconfig_module(self): import sysconfig as glo

[issue17679] sysconfig generation uses some env variables multiple times

2013-04-10 Thread Bohuslav "Slavek" Kabrda
Bohuslav "Slavek" Kabrda added the comment: I'm attaching a patch that I'm currently using to solve this. It works, but it's a bit aggressive - in the sense that it only adds a string to the sysconfig variable iff this string is not a substring of current variable value. So it may corrupt some

[issue17679] sysconfig generation uses some env variables multiple times

2013-04-09 Thread Ned Deily
Changes by Ned Deily : -- versions: +Python 2.7, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue17679] sysconfig generation uses some env variables multiple times

2013-04-09 Thread Ned Deily
Ned Deily added the comment: There definitely are configurations where some values do get duplicated in CFLAGS and LDFLAGS. In my experience this is generally harmless for builds but, as you point out, it can break tests that expect particular values. It would be nice to clean this up.

[issue17679] sysconfig generation uses some env variables multiple times

2013-04-09 Thread Bohuslav "Slavek" Kabrda
New submission from Bohuslav "Slavek" Kabrda: When compiling Python 3.3.1, I noticed that some variables like LDFLAGS or CFLAGS in sysconfig have some flags multiple times. (Which BTW breaks distutils.tests.{test_sysconfig_compiler_vars,test_sysconfig_module}) This is caused by interpretation