* Julien Cristau <jcris...@debian.org>, 2012-07-16, 15:07:
it's a plain bug in libpython2.7 AFAICT.
ACK, though it woudn't trigger if vim build system didn't do dubious
things...
I can see two ways to fix this mess:
Plan A
======
1) Fix python2.7 symbols. Add Breaks for each provider of vim-python.
2) binNMU vim.
Plan B
======
In any order:
- Fix vim build not to link config.c into the binary. (I attached a
proposed patch.)
- Fix python2.7 symbols. Add Breaks for each provider of vim-python.
Personally, I'd prefer plan B.
--
Jakub Wilk
--- a/src/configure.in
+++ b/src/configure.in
@@ -913,12 +913,7 @@
PYTHON_CFLAGS="-I${vi_cv_path_python_pfx}/include/python${vi_cv_var_python_version} -I${vi_cv_path_python_epfx}/include/python${vi_cv_var_python_version} -DPYTHON_HOME=\\\"${vi_cv_path_python_pfx}\\\""
fi
PYTHON_SRC="if_python.c"
- dnl For Mac OSX 10.2 config.o is included in the Python library.
- if test "x$MACOSX" = "xyes"; then
- PYTHON_OBJ="objects/if_python.o"
- else
- PYTHON_OBJ="objects/if_python.o objects/py_config.o"
- fi
+ PYTHON_OBJ="objects/if_python.o"
if test "${vi_cv_var_python_version}" = "1.4"; then
PYTHON_OBJ="$PYTHON_OBJ objects/py_getpath.o"
fi
--- a/src/auto/configure
+++ b/src/auto/configure
@@ -5354,11 +5354,7 @@
PYTHON_CFLAGS="-I${vi_cv_path_python_pfx}/include/python${vi_cv_var_python_version} -I${vi_cv_path_python_epfx}/include/python${vi_cv_var_python_version} -DPYTHON_HOME=\\\"${vi_cv_path_python_pfx}\\\""
fi
PYTHON_SRC="if_python.c"
- if test "x$MACOSX" = "xyes"; then
- PYTHON_OBJ="objects/if_python.o"
- else
- PYTHON_OBJ="objects/if_python.o objects/py_config.o"
- fi
+ PYTHON_OBJ="objects/if_python.o"
if test "${vi_cv_var_python_version}" = "1.4"; then
PYTHON_OBJ="$PYTHON_OBJ objects/py_getpath.o"
fi
