Compiling software with c++11 support

[Jeremy Huddleston Sequoia]

On Sep 11, 2013, at 23:00, Jeremy Huddleston Sequoia <jeremyhu at macports.org> wrote:

> 
> On Sep 11, 2013, at 22:45, Lawrence Velázquez <larryv at macports.org> wrote:
> 
>> If you do choose to switch to libc++ and rebuild all your ports, keep in mind that a successful build does not necessarily mean a successful build against libc++. A misbehaving port might quietly link against libstdc++ behind your back. Use otool -L to check your executables and libraries:
>> 
>>   % otool -L /opt/local/bin/pdflatex
>>   /opt/local/bin/pdflatex:
>>   	/opt/local/lib/libpng15.15.dylib (compatibility version 33.0.0, current version 33.0.0)
>>   	/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8)
>>   	/opt/local/lib/libpoppler.43.dylib (compatibility version 44.0.0, current version 44.0.0)
>>   	/opt/local/lib/libkpathsea.6.dylib (compatibility version 8.0.0, current version 8.1.0)
>>   	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
>>   	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
>>   %
> 
> True true.
> 
> We might consider adding a check into revupgrade, but I haven't looked at that yet.

r110973 should take care of that...

--Jeremy


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130911/8d888163/attachment.p7s>