On 02/02/2015 14:07, Kubilay Kocak wrote: > On 3/02/2015 1:03 AM, Dmitry Sivachenko wrote: >> >>> On 2 февр. 2015 г., at 2:36, Baptiste Daroussin <b...@freebsd.org> wrote: >>> >>> Hi, >>> >>> At FOSDEM I have been reported by Sevan (CCed) that the python's configure >>> scripts thinks it is forbidden to have a lib named libpython2.so.X.Y on >>> FreeBSD >>> which is wrong. >>> >>> Here is a patch that fixes it on python2 unfortunatly as a result that means >>> everything linked to libpython2.so.1 will need a bump. (same thing should be >>> done for other pythons) >>> >>> I would prefer that you guys decides when how and so on to make that change >>> happening. >>> >>> https://people.freebsd.org/~bapt/respect-the-libname-decided-by-upstream.diff >>> >>> I modified the configure script and not the configure.ac because the patch >>> is >>> not worth have to depend on autotools to regenerate the configure. >>> >> >> >> Since this is the explicit case for FreeBSD it would be nice to see what >> commit log for that change in Python's repo was. >> > > For reference: > > https://hg.python.org/cpython/diff/6fc10306bf31/configure > http://bugs.python.org/issue1044395 > > ./koobs >
Hi Guys, Any luck with this? was just digging into Python 2.7.10 for a unrelated manner and noticed the change is still there to trim the library name. Sevan _______________________________________________ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
