clang 3.4 can't be configured (part of a selfupdate)
Ken Cunningham
ken.cunningham.webuse at gmail.com
Mon Aug 1 16:05:25 PDT 2016
Interestingly, I just went to update my libmacho and libunwind to the universal variants given this conversation (already did the cxx and cxxabi ports) -- but oddly, perhaps, this seemingly fully functional 10.6.8 /libc++ system with clang-3.8, all installed through macports, has neither libmacho nor libunwind installed. But it does have the headers.
For your consideration....
Ken
port -v installed libcxxabi
The following ports are currently installed:
libcxxabi @3.7.0_1+universal (active) platform='darwin 10' archs='i386 x86_64'
port -v installed libcxx
The following ports are currently installed:
libcxx @3.7.1_0+universal (active) platform='darwin 10' archs='i386 x86_64'
port -v installed libunwind*
The following ports are currently installed:
libunwind-headers @3.7.0_1 (active) platform='darwin 10' archs='noarch'
port -v installed libmac*
The following ports are currently installed:
libmacho-headers @877.8_0 platform='darwin 10' archs='noarch'
libmacho-headers @886_0 (active) platform='darwin 10' archs='noarch'
>
>
> libcxx depends on libcxxabi which depends on libunwind and libmacho. We'd need to force all four to build +universal for that.
>
> r150880
>
> --Jeremy
>
More information about the macports-users
mailing list