Date: Fri, 31 Jul 2009 16:29:06 +0400 From: Alexander Churanov <alexanderchuranov@gmail.com> To: Mel Flynn <mel.flynn+fbsd.ports@mailing.thruhere.net> Cc: freebsd-ports@freebsd.org Subject: Re: devel/boost: new patch for testing update to 1.39 Message-ID: <3cb459ed0907310529r611cc1b1lb8a5c47b6722f6b6@mail.gmail.com> In-Reply-To: <200907300819.44453.mel.flynn%2Bfbsd.ports@mailing.thruhere.net> References: <3cb459ed0906290644x86ac44cu48fd8bba52d024f9@mail.gmail.com> <200907291356.39608.mel.flynn%2Bfbsd.ports@mailing.thruhere.net> <3cb459ed0907300420m4b0bd47cjd209aacdbbeb10da@mail.gmail.com> <200907300819.44453.mel.flynn%2Bfbsd.ports@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mel, Now It's clear. Thank you for explanation. The WITH_PYSTE was not in the options framework, that's why I've missed this part of work. I see two possible solutions: 1) Put the WITH_PYSTE variable back. 2) Create a separate port like devel/boost-pyste. The first is easy, however leads to dependeny issues like 'let's verify that boost-python-libs is installed with PYSTE support'. Provided that Pyste is actually used by someone, this may re-introduce bug ports/123927 (see http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/123927). The second is much more robust, but requires more work. This is also harder because I am not a user of Boost.Pyste. Thus, correctness verification would be expensive. Folks, is there a user of Boost.Pyste, willing to volunteer with devel/boost-pyste quality verification? Sincerely, Alexander Churanov maintainer of devel/boost-* 2009/7/30 Mel Flynn <mel.flynn+fbsd.ports@mailing.thruhere.net>: > On Thursday 30 July 2009 03:20:56 Alexander Churanov wrote: > >> I do not understand. >> >> Is it correct that you are discussing the issue of Pyste being part of >> boost and depending on gccxml port, which has issues of its own? >> >> I do not use Pyste and did not performed any specific testing of it, >> but all of boost-python-libs builds and installs, including >> dependencies. >> >> Please, describe what do you expect from ports and what do you >> observe, what negative outcome the issue has. > > The previous boost-python port had an *optional* dependency on pyste. > The current one does not. This means that boost-python now pulls in > gccxml which pulls in lang/gcc34 on anything but 6.x. > I'm currently building boost-python-libs with the pyste stuff > ifdef'd out[1] and will try to build packages kdeedu3, kdebase4, > games/wesnoth to see if there's any adverse side-effects. > > -- > Mel > > [1] > --- Makefile.orig =A0 =A0 =A0 2009-07-28 03:44:50.000000000 -0800 > +++ Makefile =A0 =A02009-07-30 07:19:26.000000000 -0800 > @@ -25,9 +25,11 @@ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0PYTHON_INCLUDES=3D"${PYTHON_INCLUDEDIR}"\ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0PYTHON_LIB_PATH=3D"${PYTHON_LIBDIR}" > > -RUN_DEPENDS+=3D =A0${PREFIX}/lib/libboost_thread.so.${BOOST_SHARED_LIB_V= ER}:${PORTSDIR}/devel/boost-libs > -RUN_DEPENDS+=3D =A0gccxml:${PORTSDIR}/devel/gccxml \ > - =A0 =A0 =A0 =A0 =A0 =A0 =A0 ${PYTHON_SITELIBDIR}/elementtree/ElementTre= e.py:${PORTSDIR}/devel/py-elementtree > +RUN_DEPENDS+=3D =A0${LOCALBASE}/lib/libboost_thread.so.${BOOST_SHARED_LI= B_VER}:${PORTSDIR}/devel/boost-libs > +RUN_DEPENDS+=3D =A0${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${POR= TSDIR}/devel/py-elementtree > +.if defined(WITH_PYSTE) > +RUN_DEPENDS+=3D =A0gccxml:${PORTSDIR}/devel/gccxml > +.endif > > =A0BUILD_DEPENDS+=3D =A0 =A0 =A0 =A0${BJAM}:${PORTSDIR}/devel/boost-jam > =A0BUILD_DEPENDS+=3D =A0 =A0 =A0 =A0${PYTHON_SITELIBDIR}/elementtree/Elem= entTree.py:${PORTSDIR}/devel/py-elementtree > @@ -39,12 +41,13 @@ > > =A0post-patch: customize-boost-build > > - > +.if defined(WITH_PYSTE) > =A0post-configure: > =A0# Configure pyste, the Boost.Python code generator > =A0 =A0 =A0 =A0@cd ${BUILD_WRKSRC}/libs/python/pyste/install && \ > =A0 =A0 =A0 =A0${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0config ${PYDISTUTILS_CONFIGUREARGS} > +.endif > > =A0do-build: > =A0# build the library > @@ -52,11 +55,12 @@ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0${SETENV} ${MAKE_ENV} ${BJAM} ${BJAM_OPTIO= NS} --prefix=3D${PREFIX}\ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0--toolset=3D${BOOST_TOOLS} --with-python > > +.if defined(WITH_PYSTE) > =A0# Build pyste, the Boost.Python code generator > =A0 =A0 =A0 =A0cd ${BUILD_WRKSRC}/libs/python/pyste/install && \ > =A0 =A0 =A0 =A0${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0build ${PYDISTUTILS_BUILDARGS} > - > +.endif > =A0# Remove non-python headers > =A0 =A0 =A0 =A0cd ${WRKSRC} && \ > =A0 =A0 =A0 =A0${FIND} boost -not -path '*python*' -delete > @@ -79,10 +83,12 @@ > =A0 =A0 =A0 =A0${FIND} boost -type f -a \! -name "*.orig"\ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-exec ${INSTALL_DATA} \{\} ${PREFIX}/inclu= de/\{\} \; > > +.if defined(WITH_PYSTE) > =A0# Install pyste, the Boost.Python code generator > =A0 =A0 =A0 =A0cd ${WRKSRC}/libs/python/pyste/install && \ > =A0 =A0 =A0 =A0${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0install ${PYDISTUTILS_INSTALLARGS} > +.endif > > =A0post-install: > =A0# display pkg-message > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3cb459ed0907310529r611cc1b1lb8a5c47b6722f6b6>