Date: Mon, 2 Feb 2015 00:36:41 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: python@FreeBSD.org Cc: Sevan Janiyan <venture37@geeklan.co.uk> Subject: Python's configure misunderstand freebsd Message-ID: <20150201233641.GH11558@ivaldir.etoilebsd.net>
next in thread | raw e-mail | index | archive | help
--hAW+M2+FUO+onfmf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. That should also be upstreamed (if one of you could do it it would be great :)) Best regards, Bapt --hAW+M2+FUO+onfmf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTOuIkACgkQ8kTtMUmk6EwihgCghnspACA2yLBEUTjrwsSelQpZ XmsAnijlm3YsPTLhmGUMT19QGvAafn4T =N/82 -----END PGP SIGNATURE----- --hAW+M2+FUO+onfmf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150201233641.GH11558>