Why does everything now want ncurses-bootstrap, which doesn't build???

[Joshua Root]

> On 23 Aug 2019, at 21:00, Joshua Root wrote:
> 
>> The reason for the *-bootstrap ports is that 10.6 doesn't come with
>> libc++. So you need to be able to build a compiler capable of building
>> libc++, while only using the system's libstdc++. That compiler is
>> clang-3.4, and it depends on a number of ports that use C++ and have
>> other dependents, so you'd want them to be using libc++. Hence the 
>> ports
>> like ncurses-bootstrap link with libstdc++ and install in a different
>> location so that the normal ncurses port can be installed too.
> 
> I understand that would be needed if you're bootstrapping a libc++ world 
> but *I think* I've already got a working libc++ compiler world:
> 
> # port installed llvm* clang*
> The following ports are currently installed:
>    clang-3.4 @3.4.2_12+analyzer+assertions (active)
>    clang-5.0 @5.0.2_3+analyzer+defaultlibcxx+emulated_tls (active)
>    clang-6.0 @6.0.1_2+analyzer+defaultlibcxx+emulated_tls (active)
>    clang-8.0 @8.0.0_0+analyzer+defaultlibcxx+emulated_tls+libstdcxx 
> (active)
>    clang_select @2_0 (active)
>    llvm-3.4 @3.4.2_12+assertions (active)
>    llvm-5.0 @5.0.2_0 (active)
>    llvm-6.0 @6.0.1_0 (active)
>    llvm-8.0 @8.0.0_0+emulated_tls (active)
>    llvm_select @2_0 (active)

It's possible that the problem will go away if you uninstall clang-3.4
and llvm-3.4. The bootstrap ports are only needed as dependencies of
those, and you shouldn't need clang-3.4 any more once you've
bootstrapped something newer.

- Josh