From owner-freebsd-ports@FreeBSD.ORG Mon Oct 28 19:03:49 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 445E169E for ; Mon, 28 Oct 2013 19:03:49 +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 8BF9B2616 for ; Mon, 28 Oct 2013 19:03:47 +0000 (UTC) Received: (qmail 42206 invoked by uid 89); 28 Oct 2013 18:57:06 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.66) by mail.grem.de with ESMTPA; 28 Oct 2013 18:57:06 -0000 Date: Mon, 28 Oct 2013 19:57:08 +0100 From: Michael Gmelin To: freebsd-ports@freebsd.org Subject: Build C++ based packages using C++11 Message-ID: <20131028195708.53325afe@bsd64.grem.de> X-Mailer: Claws Mail 3.9.2 (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: Mon, 28 Oct 2013 19:03:49 -0000 Hi, Now that most ports build ok with clang, are there any steps planned towards supporting C++11 and libc++ in the ports tree? I'm thinking of flags like NEEDS_CPP98, NEEDS_CPP11 etc. With C++14 at the horizon I expect more problems with ports depending on C++11 and even though mixing standard libraries and language revisions might build in many cases, it can lead to terrible problems at run time. Michael -- Michael Gmelin