On 10/22/13 3:42 PM, su_v wrote:
On 2013-10-23 24:12 +0200, David Evans wrote:
OS X Mavericks (10.9) is released today (Free upgrade in App Store.) Please see the following email to MacPorts developers today concerning C++ compatibility and need to build with clang++.
Note that inkscape (0.48.4) is a current issue because it doesn't build with clang++. I'm hoping that backporting the current upstream patches concerning clang compatibility for this branch will solve the problem.
Related bug reports:
- Bug #1194129 “backport fixes for clang compiler errors to the 0.48.x branch” https://bugs.launchpad.net/inkscape/+bug/1194129 (done: backported to the stable branch lp:inkscape/0.48.x; AFAIK not tested on Mavericks)
and probably:
- Bug #1232474 “FreeBSD, clang, libc++, inkscape 0.48.x rev9969: calling a private constructor of class (iterator)” https://bugs.launchpad.net/inkscape/+bug/1232474 (has patch for trunk, no backports for stable release branch)
@Markus - does revision 12701 fix bug #1232474? http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/12701
inkscape 0.48.x r9971 builds without error using Apple clang 5.0 on OS X 10.8, OS X 10.7 and Apple gcc-4.2 on OS X 10.6.
However, build fails using clang on OS X 10.9 due to libc++
Applying the uncommitted portion of Markus' patch in bug #1232474 (thanks) fixes the initial problem but build fails again this time with a TR1 namespace issue. Same results on lp:inkscape r12715. So any further changes should be applied to both.
I have filed bug #1244295 with the details. I'm not comfortable with just hacking the code so suggestions are welcome. I recognize that many developers may not have 10.9 but I have an installation available for testing. MacPorts should have a buildbot for Mavericks set up by next week.