#37678: MacPorts gcc gives malloc error on correct program using boost, Apple's gcc doesn't ------------------------------+-------------------------------- Reporter: yusuhail@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: boost libstdcxx | ------------------------------+-------------------------------- Comment (by ecronin@…): I don't believe boost is sadistic enough yet to have bjam process the headers installed, so multiple compilers could share the same $prefix/include/boost. Boost also supports versioned library names which allow you to install boost for multiple compilers into the standard location at the cost of needing -lboost_system-gcc47-mt instead of just -lboost_system. I don't know how painful it would be to make every port that depends on boost find the correct lib if we started doing this, and the work to make bjam build them is not insignificant. But then we could have a boost-headers (sub)port and boost-clang31 boost-gcc47, etc subports (here it's not just the libc++ vs libstdc++ issue, boost is so tightly coupled with the compiler used to build it you really really don't want to be using anything but exactly the same compiler with exactly the same -std= flags). This would be a significant undertaking that adfernandes has indicated in the past he's not planning to tackle (can't blame him, I'm not signing up either) but is realistically the only way to solve this problem that keeps coming up. I wish there was a way for the boost libs to just fail completely with a useful message when there is a mismatch... For mkvtoolnix, has anyone tried the latest mp-clang-devel? I thought it was C++11 compliant enough to build it now? -- Ticket URL: <https://trac.macports.org/ticket/37678#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS