From owner-freebsd-ports@freebsd.org Thu Sep 1 20:04:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 630F0BCBA2F for ; Thu, 1 Sep 2016 20:04:59 +0000 (UTC) (envelope-from ben.lavery@hashbang0.com) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55B5EDF2 for ; Thu, 1 Sep 2016 20:04:58 +0000 (UTC) (envelope-from ben.lavery@hashbang0.com) Received: from [192.168.1.78] (134.164.93.209.dyn.plus.net [209.93.164.134]) by mx.zohomail.com with SMTPS id 1472760290141409.9696926336542; Thu, 1 Sep 2016 13:04:50 -0700 (PDT) Subject: Re: codecvt and libc++ on FreeBSD 9.x To: Michelle Sullivan References: <36e5134f-ef31-ec5a-c029-9a005f4c8e8d@hashbang0.com> <57C8888D.4030400@sorbs.net> Cc: freebsd-ports@freebsd.org From: Ben Lavery Message-ID: Date: Thu, 1 Sep 2016 21:04:46 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <57C8888D.4030400@sorbs.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 20:04:59 -0000 On 09/01/16 20:59, Michelle Sullivan wrote: > Ben Lavery wrote: >> >> >> On the submission >> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212278) CPM has >> said of the issue "Second it seems that codecvt is missing, so it >> needs libc++ support" - but I'm not sure how to add this. I've tried >> adding the following which I found in multiple threads on the forums, >> but to no avail: >> >> CC=clang >> CXX=clang++ >> CPP=clang-cpp >> WITH_LIBCPLUSPLUS=yes >> >> I *think* this is because clang is too old on FreeBSD 9.3? But I'm >> not sure if I can/should reference a newer version from ports (and how >> to go about this in the proper way), and how to make this apply to >> FreeBSD 9.x only as it works fine "as is" on FreeBSD 10. > > Did you go with the base compiler or use the clang in ports? > > You might want to do that - you can also probably use GCC which is also > available in ports. > > Regards, > > Michelle Yes I did am using the base compiler, I know I can do a "BUILD_DEPENDS" to ensure a port (e.g. lang/clang35 would do, I think) is available at build time, but I'm unsure: a) if that will indeed solve my issue b) how to ensure this doesn't affect FreeBSD 10 and above builds - if there some kind of ".if FreeBSd 9"? c) how to ensure cmake uses the ports version of clang rather than base - would I modify the variables I mentioned in my original post? Many thanks, Ben