From owner-freebsd-ports@FreeBSD.ORG Thu Jun 13 01:22:59 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6A14B98F for ; Thu, 13 Jun 2013 01:22:59 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id D01801E6E for ; Thu, 13 Jun 2013 01:22:57 +0000 (UTC) Received: (qmail 4623 invoked by uid 89); 13 Jun 2013 01:16:15 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@93.215.185.65) by mail.grem.de with ESMTPA; 13 Jun 2013 01:16:15 -0000 Date: Thu, 13 Jun 2013 03:15:35 +0200 From: Michael Gmelin To: freebsd-ports@freebsd.org Subject: Are ports supposed to build and run on 10-CURRENT? Message-ID: <20130613031535.4087d7f9@bsd64.grem.de> X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jun 2013 01:22:59 -0000 Hi, I've been waiting for http://www.freebsd.org/cgi/query-pr.cgi?pr=179233 to get committed for a little while now. The person looking at it today decided to test it on 10-CURRENT, which failed (it built, but unit tests fail with all kinds of bus errors on exit). It's not entirely clear what the issue is, but since Ice is a very complex port there are many possible reasons why it might fail. I *did* test the port thoroughly and successfully on current RELEASE versions in various combinations though: - system gcc + system libstdc++ - system clang + system libstdc++ - system clang + std=c++11 + system libc++ I reproduced the problem on 10-CURRENT, the test results are: - system gcc + system libstdc++ : Build ok, Unit tests *ok* - system clang + system libstdc++: Build ok, Unit tests fail - system clang + std=c++11 + system libc++: Build fails, due to a dependency (databases/db5) not building with those flags. It looks like a problem in libc++ to me, but I didn't have much time to investigate. It might be one of those things that might just go away after a while. Building ports with libc++ and C++11 is a separate, but - for some people and software packages - important topic I will address in a separate post. But overall the port simply doesn't work correctly on HEAD and its non-release versions of clang and libc++. Marking the port as GCC only is not an option though, since building it with clang + C++11 + libc++ results in a lot more useful package and for RELEASE it *does* work correctly. For all I know this might be due to bugs in clang, a problem in Ice or something completely different. So my question is: Are we port maintainers now really supposed to make ports work with CURRENT? That would be an awful lot of extra work and I don't think I'm willing to handle this extra work, especially in case of devel/ice, devel/py-ice and devel/php5-ice, which already took a substantial amount of time to patch and test to make sure they work properly on RELEASE versions of FreeBSD. Cheers, Michael -- Michael Gmelin