captain-10.9-libc++ isn’t going to work because we haven’t populated
the 10.9-libcxx distribution yet.
The way things are going for me right now, I don’t know if I’m ever going to
have time to do that before El Capitan is released.
Somebody else needs to step up.
—Alexander
I have good
On Jul 15, 2015, at 10:10, John Lillibridge john.lillibri...@noaa.gov wrote:
Alexander Hansen alexanderk.hansen at gmail.com writes:
Oh, and as a side benefit, in principle we could start this new distribution
on github.
Alexander Hansen alexanderk.hansen at gmail.com writes:
Oh, and as a side benefit, in principle we could start this new distribution
on github.
-
Thanks Alexander. I wanted to relate my initial experiences trying to
We’ve accumulated a bunch of cruft, and I’d personally like to put 10.7 and
10.8 out to pasture after 10.11 is released.
I’m proposing the name “10.9-libc++” to denote when we first started building
with libc++. This would replace 10.7 as the real directory to which the
symlinks point on
On Jun 9, 2015, at 18:43, Alexander Hansen alexanderk.han...@gmail.com
wrote:
We’ve accumulated a bunch of cruft, and I’d personally like to put 10.7 and
10.8 out to pasture after 10.11 is released.
I’m proposing the name “10.9-libc++” to denote when we first started building
with
