On 2014-3-5 07:55 , Jeremy Huddleston Sequoia wrote: > In https://trac.macports.org/ticket/42699, Adam pointed out to me that > llvm-3.5 isn't building for him on Mavericks with released base due to the > lack of -Wl,-headerpad_max_install_names. Additionally, llvm-3.5 requires > trunk base to install on Mountain Lion and earlier.
The current release does have headerpad_max_install_names in its default ldflags. > There are also a bunch of other hacks throughout dports for libc++ that will > benefit from the next release of base. > > According to http://trac.macports.org/roadmap, 2.3.0 is scheduled for June, > but I'm wondering if we could move that up. Specifically, what are we > waiting for? June is more of an "at the latest" date. Currently waiting a little to see if trunk users find problems with the recent changes. Then we'd normally be in beta for a few weeks before a release. > Would it be worthwhile to instead cut a 2.2.x with the configure.cxx_stdlib > and -Wl,-headerpad_max_install_names changes? Probably not. - Josh _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
