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.
...
kde/krusader
...
---
Is it possible to address this issue?
Thanks,
Oleg
Étienne Magnier
unread,
Feb 19, 2014, 11:13:37 PM2/19/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to krusade...@googlegroups.com
+1 for this issue.
I'm also now on Mavericks, and would love to use Krusader on this OS.