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=ports/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 <[email protected]>: > 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 2009-07-28 03:44:50.000000000 -0800 > +++ Makefile 2009-07-30 07:19:26.000000000 -0800 > @@ -25,9 +25,11 @@ > PYTHON_INCLUDES="${PYTHON_INCLUDEDIR}"\ > PYTHON_LIB_PATH="${PYTHON_LIBDIR}" > > -RUN_DEPENDS+= > ${PREFIX}/lib/libboost_thread.so.${BOOST_SHARED_LIB_VER}:${PORTSDIR}/devel/boost-libs > -RUN_DEPENDS+= gccxml:${PORTSDIR}/devel/gccxml \ > - > ${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree > +RUN_DEPENDS+= > ${LOCALBASE}/lib/libboost_thread.so.${BOOST_SHARED_LIB_VER}:${PORTSDIR}/devel/boost-libs > +RUN_DEPENDS+= > ${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree > +.if defined(WITH_PYSTE) > +RUN_DEPENDS+= gccxml:${PORTSDIR}/devel/gccxml > +.endif > > BUILD_DEPENDS+= ${BJAM}:${PORTSDIR}/devel/boost-jam > BUILD_DEPENDS+= > ${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree > @@ -39,12 +41,13 @@ > > post-patch: customize-boost-build > > - > +.if defined(WITH_PYSTE) > post-configure: > # Configure pyste, the Boost.Python code generator > �...@cd ${BUILD_WRKSRC}/libs/python/pyste/install && \ > ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \ > config ${PYDISTUTILS_CONFIGUREARGS} > +.endif > > do-build: > # build the library > @@ -52,11 +55,12 @@ > ${SETENV} ${MAKE_ENV} ${BJAM} ${BJAM_OPTIONS} > --prefix=${PREFIX}\ > --toolset=${BOOST_TOOLS} --with-python > > +.if defined(WITH_PYSTE) > # Build pyste, the Boost.Python code generator > cd ${BUILD_WRKSRC}/libs/python/pyste/install && \ > ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \ > build ${PYDISTUTILS_BUILDARGS} > - > +.endif > # Remove non-python headers > cd ${WRKSRC} && \ > ${FIND} boost -not -path '*python*' -delete > @@ -79,10 +83,12 @@ > ${FIND} boost -type f -a \! -name "*.orig"\ > -exec ${INSTALL_DATA} \{\} ${PREFIX}/include/\{\} \; > > +.if defined(WITH_PYSTE) > # Install pyste, the Boost.Python code generator > cd ${WRKSRC}/libs/python/pyste/install && \ > ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \ > install ${PYDISTUTILS_INSTALLARGS} > +.endif > > post-install: > # display pkg-message > > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
