Re: port requires c++1y -> use cxx11 portgroup?

> On Dec 3, 2016, at 3:42 PM, Ken Cunningham > wrote: > >> C++1y and C++14 are the same. > > Apparently not exactly the same — somewhere in Pingus or its included > bits there was a specific note about changing back to c++1y as some > compilers accepted that but not c++14. "C++1y" was the work

Re: port requires c++1y -> use cxx11 portgroup?

> > > The main thing you get is that, without that portgroup, it will attempt to > build on older OS X and fail. It also supports the > https://trac.macports.org/wiki/LibcxxOnOlderSystems > workflow for those > users who have done it to ge

Re: port requires c++1y -> use cxx11 portgroup?

On Sat, Dec 3, 2016 at 3:42 PM, Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > thanks! should I add it now to Pingus, or leave it as it is do you think? The main thing you get is that, without that portgroup, it will attempt to build on older OS X and fail. It also supports the https

Re: port requires c++1y -> use cxx11 portgroup?

> > C++1y and C++14 are the same. Apparently not exactly the same — somewhere in Pingus or its included bits there was a specific note about changing back to c++1y as some compilers accepted that but not c++14. > > The cxx11 portgroup does not express the correct restrictions for C++14, > but

Re: port requires c++1y -> use cxx11 portgroup?

> On Dec 3, 2016, at 2:09 PM, Ken Cunningham > wrote: > > The pingus port I put up last night (and which Ryan so kindly fixed > while I was sleeping for a missing dependency and an error on > case-sensitive file systems - gotta love those buildbots for finding > these things - and thanks for tha

port requires c++1y -> use cxx11 portgroup?

The pingus port I put up last night (and which Ryan so kindly fixed while I was sleeping for a missing dependency and an error on case-sensitive file systems - gotta love those buildbots for finding these things - and thanks for that) requires the c++1y standard to build. Builds will fail on sys