packages: python-pygobject/python-pygobject-link.patch (NEW) - link with -l...
Jakub Bogusz
qboosh w pld-linux.org
Śro, 20 Paź 2010, 10:02:22 CEST
On Tue, Oct 19, 2010 at 02:32:51PM +0200, lisu wrote:
> Author: lisu Date: Tue Oct 19 12:32:51 2010 GMT
> Module: packages Tag: HEAD
> ---- Log message:
> - link with -lpython
>
> ---- Files affected:
> packages/python-pygobject:
> python-pygobject-link.patch (NONE -> 1.1) (NEW)
>
> ---- Diffs:
>
> ================================================================
> Index: packages/python-pygobject/python-pygobject-link.patch
> diff -u /dev/null packages/python-pygobject/python-pygobject-link.patch:1.1
> --- /dev/null Tue Oct 19 14:32:51 2010
> +++ packages/python-pygobject/python-pygobject-link.patch Tue Oct 19 14:32:46 2010
> @@ -0,0 +1,10 @@
> +--- pygobject-2.26.0/configure.ac~ 2010-09-27 17:59:54.000000000 +0200
> ++++ pygobject-2.26.0/configure.ac 2010-10-19 13:59:45.988405664 +0200
> +@@ -174,6 +174,7 @@
> + AM_PATH_GLIB_2_0(glib_required_version,,[AC_MSG_ERROR(maybe you want the pygobject-2-4 branch?)],gobject $extra_mods)
> + if test -n "$export_dynamic"; then
> + GLIB_LIBS=`echo $GLIB_LIBS | sed -e "s/$export_dynamic//"`
> ++ GLIB_LIBS="$GLIB_LIBS -lpython"
> + fi
> + PYTHON_BASENAME=`basename $PYTHON`
> + AC_SUBST([PYTHON_BASENAME])
To raczej nie jest potrzebne - moduły Pythona są wczytywane z poziomu
środowiska, więc wszystkie potrzebne symbole z libpython* mają wtedy
dostępne.
--
Jakub Bogusz http://qboosh.pl/
Więcej informacji o liście dyskusyjnej pld-devel-pl