harfbuzz-icu 0.9.37_0 build fails on 10.7.5
ryandesign at macports.org
Sat Dec 20 09:58:38 PST 2014
On Dec 20, 2014, at 11:55 AM, René J.V. Bertin wrote:
> On Saturday December 20 2014 11:35:06 Ryan Schmidt wrote:
>> IIUC, icu only adds --std=c++0x to its pkg-config files and icu-config script if it detects that the compiler used to compile icu supports it. So it should only do that when compiling using clang. That wouldn't be the case on 10.6 or earlier.
> Wouldn't that depend on whether the user has Xcode 4.2 (or whatever the 10.6-compatible version is) installed, and thus clang-3.0?
MacPorts defaults to llvm-gcc-4.2 with Xcode 4.0, 4.1 and 4.2. MacPorts used to default to clang with Xcode 4.2, but this was changed.
>> It seems wrong to me that icu would put flags like --std=c++0x into its config files, and I've reported that bug to the developers of icu.
> And that would probably depend on whether a libicu built with C++11 is ABI-compatible with one built as regular C++. Is it?
I have no idea. I hope so. We'll see what the developers say.
More information about the macports-users