Just a note that 1.49 has been released. Regarding the exp-run results and this comment http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156253#reply7 - I think that the number of the failing ports is sufficiently small and the current boost version is sufficiently outdated to justify breaking those ports and putting onus on their maintainers and upstreams.
I suspect that in some case just updating the ports to the latest upstreams could fix the problems. http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.8-exp.20120127093941/libreoffice-3.4.5.log This bug report seems to describe the same issue and has fixes: https://qa.mandriva.com/show_bug.cgi?id=64945 https://bugs.freedesktop.org/show_bug.cgi?id=43139 http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/a.8-exp.20120127093941/gstreamer-qt4-0.10.1_1.log http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/a.8-exp.20120127093941/wesnoth-1.8.6.log Googling for <error: 'boost::BOOST_FOREACH' has not been declared> provides a number of recipes for a fix - the problem seems to be universally caused by #define foreach BOOST_FOREACH somewhere in (non-boost) source code. http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/a.8-exp.20120127093941/gstreamer-qt4-0.10.1_1.log Again google helps (<Parse error at "BOOST_JOIN">): https://bugreports.qt-project.org//browse/QTBUG-22829 Every problem seems to have a solution already. We are not the first to use newer boost :-) But it's unreasonable to expect that a single person should fix all the problems in advance. The task should be parallelized among maintainers of the dependent ports (and their users with hacking skills). -- Andriy Gapon _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
