[avg@FreeBSD.org: Re: ports/156253: [exp-run] [patch] Update devel/boost-* from 1.45 to 1.46.1]

Mark Linimon linimon at lonesome.com
Sun Mar 4 07:56:18 UTC 2012

At some point FreeBSD needs to update to the latest version of boost
One or more of your ports was shown to break during our last -exp run:


Can each of you take a look to see if the latst version of the port from
upstream fixes known problems with boost?



for reference:

aqsis-                  gahr at FreeBSD.org
cgal-                   wenheping at gmail.com
eiskaltdcpp-lib-        gelraen.ua at gmail.com
galaxyhack-             ports at FreeBSD.org
gigi-                   oliver at FreeBSD.org
gstreamer-qt4-          fluffy at FreeBSD.org
lander-                 amdmi3 at FreeBSD.org
libYGP-                 ports at FreeBSD.org
libreoffice-            office at FreeBSD.org
libtorrent-rasterbar-   dougb at FreeBSD.org
luxrender-              danfe at FreeBSD.org
merkaartor-             dev2 at heesakkers.info
mkvtoolnix-             multimedia at FreeBSD.org
openlierox-             amdmi3 at FreeBSD.org
openvrml-               ports at FreeBSD.org
plee-the-bear-          amdmi3 at FreeBSD.org
ros-common-             rene at FreeBSD.org
scribe-                 jnlin at csie.nctu.edu.tw
simgear-                martymac at FreeBSD.org
springlobby-            amdmi3 at FreeBSD.org
wesnoth-                philip at FreeBSD.org

----- Forwarded message from Andriy Gapon <avg at FreeBSD.org> -----

Date: Sat, 03 Mar 2012 16:35:52 +0200
From: Andriy Gapon <avg at FreeBSD.org>
To: bug-followup at FreeBSD.org, churanov.port.maintainer at gmail.com
Subject: Re: ports/156253: [exp-run] [patch] Update devel/boost-* from 1.45
	to 1.46.1
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:10.0.2) Gecko/20120221 Thunderbird/10.0.2

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.

This bug report seems to describe the same issue and has fixes:

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.

Again google helps (<Parse error at "BOOST_JOIN">):

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

----- End forwarded message -----

More information about the freebsd-office mailing list