Re: Handling C++11

2017-01-16 Thread Mojca Miklavec
On 16 January 2017 at 21:03, Ken Cunningham wrote: > Octave builds and runs great on older systems right now when they are > upgraded to libc++ per the current instructions. Except on 10.5, I guess? Mojca

Please upgrade ansible to the latest version 2.2.1 (security fixes)

2017-01-16 Thread Johannes Kastl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, ansible release 2.2.1 yesterday, which contains a fix for a critical issue. Can someone upgrade the port to 2.2.1, please? https://trac.macports.org/ticket/53332#ticket Johannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Using Gnu

Re: Handling C++11

2017-01-16 Thread Marcus Calhoun-Lopez
> Apple's lawyers don't think so, so you cannot redistribute anything combining > Apple libraries with it. (Since you can't avoid libSystem, this means you > cannot redistribute binaries.) > > It's not a question of what makes sense to you, it's not a question of what > would be convenient. Ap

Re: Handling C++11

2017-01-16 Thread Ken Cunningham
Octave builds and runs great on older systems right now when they are upgraded to libc++ per the current instructions. $ port -v installed octave The following ports are currently installed: octave @4.2.0_1+accelerate+app+docs+fltk+gfortran+graphicsmagick+qt4+sound platform='darwin 10' archs='x8

Re: Handling C++11

2017-01-16 Thread Brandon Allbery
On Mon, Jan 16, 2017 at 1:48 PM, Marcus Calhoun-Lopez wrote: > > > gcc 5.1 libstdc++ is GPL3 and poses significant license issues with > respect to distributing binaries, among others. > Again, there may be something important I am missing, but isn’t there a > GCC runtime library exceptions that

Re: Handling C++11

2017-01-16 Thread Marcus Calhoun-Lopez
> The *only* time you should use a libstdc++ different from the system-provided > one (or ones, on 10.7) is the current LibcxxOnOlderSystems --- which > explicitly loses compatibility with all Apple-provided C++ libraries Please forgive my ignorance, but doesn’t setting _GLIBCXX_USE_CXX11_ABI=0

Re: Handling C++11

2017-01-16 Thread Brandon Allbery
On Mon, Jan 16, 2017 at 1:21 PM, Marcus Calhoun-Lopez wrote: > At the risk of rehashing a closed topic, I would like to propose a new way > of handling C++11 (especially on older systems). > I have opened three tickets that I hope, together, would solve some of the > issues raised previously. > >

Handling C++11

2017-01-16 Thread Marcus Calhoun-Lopez
At the risk of rehashing a closed topic, I would like to propose a new way of handling C++11 (especially on older systems). I have opened three tickets that I hope, together, would solve some of the issues raised previously. [1] https://trac.macports.org/ticket/53194 [2] https://trac.macports.or

Re: [macports-base] tag release_2_3_4 deleted (was d92ac26)

2017-01-16 Thread Rainer Müller
On 2017-01-16 03:13, Ryan Schmidt wrote: > >> On Jan 15, 2017, at 07:22, Rainer Müller wrote: >> >> Rainer Müller (raimue) pushed a change to tag release_2_3_4 >> in repository macports-base. >> >> *** WARNING: tag release_2_3_4 was deleted! *** >> >> was d92ac26 merge https://trac.macports.

Re: Template for pull requests

2017-01-16 Thread Mojca Miklavec
On 15 January 2017 at 23:57, Ryan Schmidt wrote: >> On Jan 15, 2017, at 02:44, Mojca Miklavec wrote: >> >> What do others think of adding some templates to our repos? > > I often find them annoying in other projects because they ask the wrong > questions. Can we find the right questions to ask? *