standard way to require c++11?

[Lawrence Velázquez]

On Apr 21, 2015, at 5:14 AM, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote:

> On Apr 20, 2015, at 23:51, Mihai Moldovan <ionic at macports.org> wrote:
>> 
>> Yes, that would be adding a new dependency on libgcc and FSF GCC for all C++ ports. But so does using libc++ on 10.6. Implicitly at least. Fortunately that doesn't add dependencies on 10.7 and higher.
>> 
>> For specific ports, yes. In general, muniversal might take of that. But it doesn't make a lot of sense to change our ports base to muniversal, if we can salvage the current state by using clang. Which implies libc++. Gotcha.
> 
> What does muniversal have to do with anything?

I think Mihai is thinking about using the portgroup's automatic lipo(1)-ing as a hacky substitute for a proper GCC driver-driver.

vq