[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: > > I've committed a patch which does just this (in r85422). Hopefully it > > won't break anything. > > Could I convince you to patch 2.7 as well? It was backported in r86848. This means it should be available in 2.7.2. -- ___

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Landreville added the comment: > I've committed a patch which does just this (in r85422). Hopefully it > won't break anything. Could I convince you to patch 2.7 as well? -- nosy: +TheoLandreville, benjamin.peterson ___ Python tracker

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: > These changes cause some regressions: > - distutils builds third-party extensions with LDFLAGS, which were > used to build CPython. (This is more important regression.) > This problem concerns Python 2.7 and 3.2. Well, is this a problem? This sounds like th

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Arfrever Frehtes Taifersar Arahesis added the comment: These changes cause some regressions: - distutils builds third-party extensions with LDFLAGS, which were used to build CPython. (This is more important regression.) This problem concerns Python 2.7 and 3.2. - distutils builds third-party

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Changes by Antoine Pitrou : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: > However, since the Makefile now explicitly appends PY_LDFLAGS to > LDSHARED, we could also stop doing so in ./configure. I've committed a patch which does just this (in r85422). Hopefully it won't break anything. -- _

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: The cause for the failure seems to be a bug in the dreaded _parse_makefile(). When you give it a Makefile such as: LDFLAGS=-foo PY_LDFLAGS=-bar LDSHARED=$(CC) -shared ${LDFLAGS} $(PY_LDFLAGS) It outputs the following variables: {'CC': '', 'LDFLAGS': '-foo',

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Martin v. Löwis added the comment: Notice that the error shows further up in the output, at the point where the test was actually run: gcc: ${LDFLAGS}: No such file or directory -- ___ Python tracker

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: Apparently, the error message is: gcc: ${LDFLAGS}: No such file or directory -- ___ Python tracker ___

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: There are now failures on the FreeBSD 7.2 buildbot: == ERROR: test_build_ext (distutils.tests.test_build_ext.BuildExtTestCase) --

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: Backported to 2.7 in r85358. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> pending ___ Python tracker ___ __

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: Committed to 3.x in r85353. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Changes by Georg Brandl : -- priority: deferred blocker -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Éric Araujo added the comment: I agree. This expert is not me, and my reply was only pragmatic. Martin: This is a bug about LDSHARED vs. LDFLAGS vs. PY_LDFLAGS vs. CONFIGURE_LDFLAGS. Could you maybe shed some light about the difference between these configure variables and review the small pa

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: > I agree with Georg: The patch seems not to make things worse, and if > it makes the tests pass, I think it should be committed. Antoine, you > decide if you want to commit it now or wait for Tarek’s review. Well, ideally, someone should have knowledge of what

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Éric Araujo added the comment: I agree with Georg: The patch seems not to make things worse, and if it makes the tests pass, I think it should be committed. Antoine, you decide if you want to commit it now or wait for Tarek’s review. -- ___ Python

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Antoine Pitrou added the comment: Other patch, fixes all failures. -- Added file: http://bugs.python.org/file18758/m32-2.patch ___ Python tracker ___

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Changes by Łukasz Langa : -- Removed message: http://bugs.python.org/msg115640 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Łukasz Langa added the comment: This was broken in r83837 with a patch for issue #5504. -- nosy: +lukasz.langa ___ Python tracker ___

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Georg Brandl added the comment: It is however not important enough to block 3.2a2. -- priority: release blocker -> deferred blocker ___ Python tracker ___ ___

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Georg Brandl added the comment: Patch looks like it at least can't make things worse to me. linker_exe should probably also get LDFLAGS (but not LDSHARED). -- nosy: +georg.brandl ___ Python tracker __

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Éric Araujo added the comment: May be related to #4010 and #9047 The bug report that triggered the edits to configure is #9189 -- ___ Python tracker ___

[issue9437] can't build extensions with non-default ldflags (e.g. -m32)

Changes by Antoine Pitrou : -- priority: high -> release blocker title: test_distutils failure with -m32 -> can't build extensions with non-default ldflags (e.g. -m32) ___ Python tracker ___