codecvt and libc++ on FreeBSD 9.x

Ben Lavery ben.lavery at hashbang0.com
Thu Sep 1 20:04:59 UTC 2016


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



More information about the freebsd-ports mailing list