From owner-freebsd-ports@FreeBSD.ORG Mon May 14 10:07:28 2012 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63A551065678; Mon, 14 May 2012 10:07:28 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CE1F08FC0C; Mon, 14 May 2012 10:07:26 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA22503; Mon, 14 May 2012 13:07:24 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1STsBY-000FpW-Ea; Mon, 14 May 2012 13:07:24 +0300 Message-ID: <4FB0D95A.4070003@FreeBSD.org> Date: Mon, 14 May 2012 13:07:22 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 MIME-Version: 1.0 To: Max Brazhnikov References: <1d5064564cfc0d44c1b2c8c52ed0aaa7@frozen-zone.org> <201205140951.18685.makc@freebsd.org> In-Reply-To: <201205140951.18685.makc@freebsd.org> X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 14 May 2012 11:24:41 +0000 Cc: boost-ports , Armin Pirkovitsch , fiziologus@gmail.com, ports@FreeBSD.org, dev2@heesakkers.info, Alexander Churanov , freebsd-ports@FreeBSD.org, sem@FreeBSD.org, linimon@lonesome.com, martymac@FreeBSD.org Subject: Re: Boost ports update X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2012 10:07:28 -0000 on 14/05/2012 12:51 Max Brazhnikov said the following: > On Mon, 14 May 2012 10:04:45 +0200, Armin Pirkovitsch wrote: >> Hi Alex, >> >> is there anything we can do to help you with the update to 1.48 right >> now? >> The default release cycle of boost suggests that 1.50 will soon be >> released (although we might have some time since there have been >> questions about the release plan for 1.50 and no definite answers to it >> yet) >> >> It would be nice to have 1.48 in ports prior to that release so we can >> have a go at 1.50 as soon as it has been released... > > Here's the list of ports that fails with new boost: > http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-8-exp-latest/index_edited.html > > Patches and fixes are welcome. But I'm going to commit the update soon anyway. Thank you! For the ports like cgal where the error(s) result from interaction between boost and Qt moc there are a few workarounds, but not proper fix yet (it seems): - a cgal specific one: http://cgal-discuss.949826.n4.nabble.com/PATCH-prevent-Qt-s-moc-from-choking-on-BOOST-JOIN-td4081602.html - more general: https://bugreports.qt-project.org/browse/QTBUG-22829 The general theme is to use Q_MOC_RUN to guard against headers that moc doesn't grok. -- Andriy Gapon