Changes between Version 1 and Version 2 of Ticket #61775, comment 4


Ignore:
Timestamp:
Dec 8, 2020, 1:50:16 AM (4 years ago)
Author:
mascguy (Christopher Nielsen)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #61775, comment 4

    v1 v2  
    22> MacPorts uses libc++ by default on 10.6 and later. Are you sure that mame is using libstdc++? If it is, that is a bug that should be fixed; it should use the C++ stdlib that MacPorts tells it to.
    33
    4 No, you're right... Mame is using libc++, rather than libstdc++. I wanted to log this ASAP, to ensure folks know I'm working these issues. But was clearly a bit too hasty. LOL
     4No, you're right... Mame is using libc++, rather than libstdc++.
    55
    66As for the issue, I've built with both Clang 9 and 10 [the MacPorts versions], and it fails in both cases. So... does that mean the same issue exists in both LLVM 9, as well as LLVM 10... but only on MacOS 10.8?