cppunit requires C++11 capable compiler now

[Michael Dickens]

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:                    port:cppunit 
./multimedia/dirac/Portfile:depends_lib     port:cppunit
./net/ola/Portfile:depends_build       port:cppunit \
./science/gnuradio/Portfile:    port:cppunit \
./science/gr-dvbs/Portfile:                    port:cppunit \
./science/gr-dvbs2/Portfile:                    port:cppunit \
./science/gr-dvbt/Portfile:                    port:cppunit \
./science/gr-fosphor/Portfile:    port:cppunit \
./textproc/librevenge/Portfile:                port:cppunit

Some of the gr-* ports don't actually use cppunit; it's just legacy
carryover since GR does & many out-of-tree modules do too. So, at most
12 according to my quick search. That's fixable within MacPorts.

I'll be committing updates for GR tonight or tomorrow for the noted
ticket, as well as fixing the relevant gr-* ports to not require cppunit
if they actually don't (e.g., gr-fosphor doesn't need it, but will
require a patch to fix it). - MLD

On Mon, May 1, 2017, at 08:06 PM, 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.
> 
> https://trac.macports.org/ticket/54078