Bug#566842: [Patch] Use Python's BASEMODLIBS for linking

[Bram Moolenaar]

James -

> Vim's configure script currently extracts the value of MODLIBS from
> Python's config/Makefile as part of the process for determining which
> libraries to link against when building if_python.c.
> 
> As described below, this is problematic as LOCALMODLIBS (which MODLIBS
> includes) is only supposed to be used when building the Python
> interpreter.  As such, it may link in extra libraries than are actually
> needed for Vim's use of Python.
> 
> I've attached Michael Bienia's patch which updates configure.in to use
> BASEMODLIBS instead of MODLIBS.
> 
> On Mon, Jan 25, 2010 at 03:03:51PM +0100, Michael Bienia wrote:
> > Hello,
> >=20
> > vim's configure script uses MODLIBS from python's config/Makefile to
> > know to link against which libs. As MODLIBS uses LOCALMODLIBS for it's
> > value and as I got told that LOCALMODLIBS shouldn't be used for python
> > extensions (I assume this applies here too as vim links against
> > libpython2.x like python extensions):
> >=20
> > "LOCALMODLIBS is a macro used to link the python binary against libaries
> > needed for the binary. It must not used to link extensions."
> > (from Matthias Klose in an Ubuntu bug)

Thanks.  I'll add it to the todo list for Vim 7.3.

- Bram

-- 
hundred-and-one symptoms of being an internet addict:
80. At parties, you introduce your spouse as your "service provider."

 /// Bram Moolenaar -- Bram at Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///