I doubt this is possible, but it strikes me that a number of big ports, like
clang-8.0, are actually forced in the portfile to build against libc++.
And my 10.6.8 system is configured to use stdlib=libc++.
But base can't rationalize this due to I suppose lack of any data showing this
is how thi
On 2019-4-1 15:34 , Ken Cunningham wrote:
> I doubt this is possible, but it strikes me that a number of big ports, like
> clang-8.0, are actually forced in the portfile to build against libc++.
>
> And my 10.6.8 system is configured to use stdlib=libc++.
>
> But base can't rationalize this due
On Mon, 1 Apr 2019 at 06:34, Ken Cunningham wrote:
>
> I doubt this is possible, but it strikes me that a number of big ports, like
> clang-8.0, are actually forced in the portfile to build against libc++.
>
> And my 10.6.8 system is configured to use stdlib=libc++.
>
> But base can't rationalize
Well blow me over, Josh. It does actually work.
I know all the clang ports clang-3.7 and up are built against libc++.
On my 10.6.8 system configured with cxx_stdlib=libc++,
sudo port -v -b install clang-6.0 cxx_stdlib=libstdc++
downloads a perfectly workable clang-6.0 binary from the MacPorts
