Date: Mon, 2 Feb 2015 17:03:41 +0300 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: Sevan Janiyan <venture37@geeklan.co.uk>, python@FreeBSD.org Subject: Re: Python's configure misunderstand freebsd Message-ID: <6D628C1D-D289-4FB0-BC43-141B1828204B@gmail.com> In-Reply-To: <20150201233641.GH11558@ivaldir.etoilebsd.net> References: <20150201233641.GH11558@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 2 =D1=84=D0=B5=D0=B2=D1=80. 2015 =D0=B3., at 2:36, Baptiste = Daroussin <bapt@FreeBSD.org> wrote: >=20 > Hi, >=20 > 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. >=20 > 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) >=20 > I would prefer that you guys decides when how and so on to make that = change > happening. >=20 > = https://people.freebsd.org/~bapt/respect-the-libname-decided-by-upstream.d= iff >=20 > 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. >=20 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6D628C1D-D289-4FB0-BC43-141B1828204B>