Mavericks
Apple released Mavericks today, and MacPorts works great on the new OS (assuming you use trunk/base). However, there is one big change that I want to point out to other MacPorts developers: the C++ runtime. The default C++ runtime is now libc++. libstdc++ is still available for binary compatibility, but newly built applications and frameworks should use libc++. This means that clang++ should be used for all C++ code since g++ does not support libc++. If a port uses C++ and fails to build with clang, it will not be supported on Mavericks (unless it does not export nor utilize C++ APIs to/from other ports). At this point, most C++ ports just work with libc++, so most users will be able to install their ports on Mavericks. One of the main reasons ports fail to build with libc++ is the tr1 namespace. If you see build errors about missing tr1 headers, please see this website for information: http://cplusplusmusings.wordpress.com/2013/06/03/whats-up-with-tr1-and-c11-and-libc/ Here is the list of ports which are currently listed as not working on Mavericks (mainly due to C++ issues). If you need any of these ports, please work with maintainers and developers to address the issues. aqua/qt4-mac archivers/libpar2 devel/openfst devel/quickfix gnome/mlview graphics/agave graphics/dcmtk graphics/enblend graphics/exact-image graphics/inkscape graphics/lib2geom graphics/podofo kde/krusader lang/chapel math/classias math/eigen math/gnudatalanguage math/octave multimedia/lmms multimedia/mp4v2 net/mediatomb net/obby science/arb science/bali-phy science/ds9 science/eo science/htcondor science/magicspp science/solid science/swarm textproc/cuneiform textproc/mgizapp textproc/opensp textproc/pialign textproc/sword Thanks, Jeremy smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mavericks
Am 22.10.2013 um 23:57 schrieb Jeremy Huddleston Sequoia: [..] Here is the list of ports which are currently listed as not working on Mavericks (mainly due to C++ issues). If you need any of these ports, please work with maintainers and developers to address the issues. [..] textproc/opensp [..] I raise my hand for textproc/opensp. I need opensp working under Maverick, together with p5-sgml-parser-opensp, as an essential part of a local installation of http://validator.w3.org. Regards, Sierk Bornemann signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mavericks
In the blog post you link to, it mentions a tool called cpp11-migratehttp://clang.llvm.org/extra/cpp11-migrate.html, which has since been renamed to clang-modernizehttp://clang.llvm.org/extra/clang-modernize.html. Could we have this be a sub-port of at least one of the Macports clang ports, so as to make it easier for developers to make this transition? Heck, if we install the clang-modernize tool, we could even run it ourselves in the portfiles that need it while we wait for the developers to do it themselves... On Tue, Oct 22, 2013 at 5:57 PM, Jeremy Huddleston Sequoia jerem...@macports.org wrote: Apple released Mavericks today, and MacPorts works great on the new OS (assuming you use trunk/base). However, there is one big change that I want to point out to other MacPorts developers: the C++ runtime. The default C++ runtime is now libc++. libstdc++ is still available for binary compatibility, but newly built applications and frameworks should use libc++. This means that clang++ should be used for all C++ code since g++ does not support libc++. If a port uses C++ and fails to build with clang, it will not be supported on Mavericks (unless it does not export nor utilize C++ APIs to/from other ports). At this point, most C++ ports just work with libc++, so most users will be able to install their ports on Mavericks. One of the main reasons ports fail to build with libc++ is the tr1 namespace. If you see build errors about missing tr1 headers, please see this website for information: http://cplusplusmusings.wordpress.com/2013/06/03/whats-up-with-tr1-and-c11-and-libc/ Here is the list of ports which are currently listed as not working on Mavericks (mainly due to C++ issues). If you need any of these ports, please work with maintainers and developers to address the issues. aqua/qt4-mac archivers/libpar2 devel/openfst devel/quickfix gnome/mlview graphics/agave graphics/dcmtk graphics/enblend graphics/exact-image graphics/inkscape graphics/lib2geom graphics/podofo kde/krusader lang/chapel math/classias math/eigen math/gnudatalanguage math/octave multimedia/lmms multimedia/mp4v2 net/mediatomb net/obby science/arb science/bali-phy science/ds9 science/eo science/htcondor science/magicspp science/solid science/swarm textproc/cuneiform textproc/mgizapp textproc/opensp textproc/pialign textproc/sword Thanks, Jeremy ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
