Hanspeter,
I would also point out that the reason that the boost1.xx releases
prior to boost1.53 don't exist on 10.9 is that
boost1.53 was the first release sufficiently patched for libc++ to properly
build against the new default c++ library
on 10.9. If you had problems building boost1.55 against the newer Xcode
5.1, there are patches back ported from
upstream to fix that…
https://trac.macports.org/browser/trunk/dports/devel/boost/files/patch-atomic.diff
Jack
On Sat, Apr 26, 2014 at 12:14 PM, Jack Howarth <howarth.at.f...@gmail.com>wrote:
> Hanspeter,
> What is the logic behind making boost1.55 build against the
> g++-fsf-4.8 compiler instead of clang++ on 10.9 and later? By doing that,
> you require any program that links against boost1.55 and all of its support
> libraries to be built with g++-fsf-4.8. We were very careful when Mavericks
> landed to make sure that boost1.53 properly built against libc++ from
> clang++ rather than any of the libstdc++ releases (system or fsf gcc). This
> seems like a major regression in the packaging compared to boost1.53. I am
> surprised you resorted to that as the newer boost release should have even
> more libc++ related fixes than 1.53 did.
> Jack
>
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
