Re: cppunit requires C++11 capable compiler now

> On May 1, 2017, at 20:06, Ryan Schmidt wrote: > > Yes it looks like cppunit now requires C++11, which means everything that > requires cppunit now requires C++11 too. Which means problems for users of > macOS versions earlier than El Capitan. > >

Re: cppunit requires C++11 capable compiler now

Luckily the number of ports affected is pretty small (found via a grep): ./graphics/agave/Portfile:port:cppunit \ ./graphics/libcdr-0.1/Portfile:port:cppunit ./graphics/libvisio-0.1/Portfile:port:cppunit \ ./graphics/podofo/Portfile:

Re: cppunit requires C++11 capable compiler now

Yes it looks like cppunit now requires C++11, which means everything that requires cppunit now requires C++11 too. Which means problems for users of macOS versions earlier than El Capitan. https://trac.macports.org/ticket/54078 > On May 1, 2017, at 11:41, Richard L. Hamilton

py-pyqt5 and qt56

How can I install py-pyqt5 with an older version of qt5? There are subports for python but not for qt. $ sudo port install py-pyqt5 Password: ---> Computing dependencies for py-pyqt5 Error: Can't install qt5-qtscript because conflicting ports are active: qt56-qtbase Error: Follow

Re: cppunit requires C++11 capable compiler now

That was it - reverting cppunit back to @1.13.2_0 (rather than the new @1.14.0_0) gets rid of the rev-upgrade problem. > On May 1, 2017, at 12:35, Richard L. Hamilton wrote: > > To make it worse, a recent update (almost certainly to cppunit) causes dirac > to appear in port

Re: cppunit requires C++11 capable compiler now

To make it worse, a recent update (almost certainly to cppunit) causes dirac to appear in port rev-upgrade, and then fail to build. main.log-dirac.txt.gz Description: GNU Zip compressed data > On May 1, 2017, at 12:23, Richard L. Hamilton wrote: > > This upgrade needed

cppunit requires C++11 capable compiler now

This upgrade needed intervention to work on Snow Leopard; cppunit may not work with whatever the default compiler happens to be: configure: error: *** A compiler with support for C++11 language features is required. Workaround: port upgrade cppunit configure.compiler=macports-gcc-5

Re: Do I need +universal to be used when installing ports?

Many thanks to the 5 people who wrote in answer to my query about using +universal. Your contributions all pointed the same way so I am now fully convinced that I have NEVER needed i386 and will not be using +universal in the future. Your help has been invaluable and I’m very grateful. Barrie.