[issue18096] bad library order returned by python-config.in

2014-10-02 Thread Matthias Klose
Matthias Klose added the comment: fixed in 2.7, 3.4 and 3.5 -- resolution: -> fixed status: open -> closed versions: +Python 2.7 -Python 3.3 ___ Python tracker ___ _

[issue18096] bad library order returned by python-config.in

2014-10-01 Thread Roundup Robot
Roundup Robot added the comment: New changeset 6316475af62d by doko in branch '2.7': - Issue #18096: Fix library order returned by python-config. https://hg.python.org/cpython/rev/6316475af62d New changeset b826ba76d1ce by doko in branch '3.4': - Issue #18096: Fix library order returned by pytho

[issue18096] bad library order returned by python-config.in

2014-10-01 Thread Logan Chien
Logan Chien added the comment: It seems that this is still reproducible with Python 3.5 (dev) by running: $ gcc test.c `python3-config --includes --ldflags` cpython-install/lib/python3.5/config-3.5m/libpython3.5m.a(pytime.o): In function `_PyTime_ObjectToTime_t': cpython-build/../cpython/Pytho

[issue18096] bad library order returned by python-config.in

2013-10-14 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- components: +Build, Demos and Tools nosy: +dmalcolm, doko stage: -> patch review versions: +Python 3.4 ___ Python tracker ___

[issue18096] bad library order returned by python-config.in

2013-10-14 Thread Georg Brandl
Changes by Georg Brandl : -- nosy: +barry, ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue18096] bad library order returned by python-config.in

2013-05-29 Thread David Taylor
New submission from David Taylor: Misc/python-config.in returns a bad library order when given the --ldflags or --libs arguments. A library should be listed *BEFORE* those libraries that it depends upon. The python library depends upon all the other libraries listed, but it is listed last --