> On Jan 24, 2016, at 1:42 AM, Vincent Habchi wrote:
>
>> Sure. And it is probably also very easy to introduce regressions that way if
>> the #ifdefs aren't already in place.
>
> Yeah, that’s right. Every cloud has its silver lining. Or the contrary for
> that matter.
>
On Monday January 25 2016 19:39:26 Ryan Schmidt wrote:
>I was under the impression that Apple already compressed the files and
>programs installed with the operating system, using HFS compression, ever
>since taking up less disk space was listed as a feature of Snow Leopard.
Yeah, I thought so
On Jan 24, 2016, at 11:15 PM, Jeremy Huddleston Sequoia wrote:
> What benefit does "cxx.require_global_libc++ no" have over the current
> approach of just doing:
>
>configure.cxx_stdlib libc++
>depends_lib-append port:libcxx
Or I was going to suggest:
PortGroupcxx11 1.0
We've had this discuss before, how to do C++11 for libstdc++ and libc++.
The cxx11 PortGroup implements C++11 compliance for libc++ only. It
errors out when using libstdc++.
What Mojca is asking is whether we can add an implementation for when
using libstdc++, and I am on board with agreeing on
> On Jan 25, 2016, at 08:04, Michael Dickens wrote:
>
> We've had this discuss before, how to do C++11 for libstdc++ and libc++.
>
> The cxx11 PortGroup implements C++11 compliance for libc++ only. It
> errors out when using libstdc++.
>
> What Mojca is asking is
> On Jan 25, 2016, at 09:29, Mojca Miklavec wrote:
>
> (Even more than that I would really like to see the buildbots with
> libc++ as their default stdlib being set up.)
As far as I know nothing has changed on this front. I'm totally willing to set
up libc++ build slaves for 10.6, 10.7 and
> On Jan 25, 2016, at 09:29, Mojca Miklavec wrote:
>
> On 25 January 2016 at 18:11, Jeremy Huddleston Sequoia wrote:
>>> On Jan 25, 2016, at 08:04, Michael Dickens wrote:
>>>
>>> We've had this discuss before, how to do C++11 for libstdc++ and libc++.
>>>
>>> The cxx11
On 25 January 2016 at 18:11, Jeremy Huddleston Sequoia wrote:
>> On Jan 25, 2016, at 08:04, Michael Dickens wrote:
>>
>> We've had this discuss before, how to do C++11 for libstdc++ and libc++.
>>
>> The cxx11 PortGroup implements C++11 compliance for libc++ only. It
>> errors out when using