port upgrade harfbuzz 1.4.5 to 1.7.2_0 fails

[tomemm]

sudo port upgrade harfbuzz failed. cleaned and retried with same failure. no mention in hotlist, nor relavency in trac search. log file included.

OS X Lion 10.7.5 on a 2.7 GHz Intel Core i7 Mac Mini with 8 GB.

[ryandesign (Ryan Carsten Schmidt)]

Huh.

:info:build Undefined symbols for architecture x86_64:
:info:build   "OT::KernOT::SubTableWrapper::min_size", referenced from:
:info:build       OT::KernTable<OT::KernOT>::sanitize(OT::hb_sanitize_context_t*) const in libharfbuzz_la-hb-ot-font.o
:info:build   "OT::KernAAT::SubTableWrapper::min_size", referenced from:
:info:build       OT::KernSubTableWrapper<OT::KernAAT::SubTableWrapper>::sanitize(OT::hb_sanitize_context_t*) const  in libharfbuzz_la-hb-ot-font.o
:info:build ld: symbol(s) not found for architecture x86_64

No idea.

Our Lion buildbot worker is offline at the moment so I don't know if we see the same problem there. But it built 1.7.1 successfully, and 1.7.2 built successfully on the buildbot workers for all the other macOS versions.

[nerdling (Jeremy Lavergne)]

This is also an issue for 10.6.8.

[ryandesign (Ryan Carsten Schmidt)]

It's not an issue on our buildbot workers on any macOS version. Maybe an undeclared opportunistically used dependency?

Here's an upstream bug report; they also have no idea: ​https://github.com/harfbuzz/harfbuzz/issues/853

[ryandesign (Ryan Carsten Schmidt)]

The attached log was on Lion with llvm-gcc-4.2. Looks like I already blacklisted llvm-gcc-4.2 in the port in [d30e3009188e928918c21a241e613aecfccc1844/macports-ports] due to this problem. So why are you still seeing the problem? Can you attach your log?

[nerdling (Jeremy Lavergne)]

cannot initialize a parameter of type 'volatile long long *' with an rvalue of type 'OT::post::accelerator_t '

[nerdling (Jeremy Lavergne)]

Attached my logs.

Looking closer, I see it's a different an issue:

./hb-open-type-private.hh:1121:11: error: cannot initialize a parameter of type 'volatile long long *' with an rvalue of type 'OT::post::accelerator_t **'

[ryandesign (Ryan Carsten Schmidt)]

Ok, I see you're using clang 139 from Xcode 4.0.2. I don't see the problem with clang 211 from Xcode 4.2. And on Xcode 3, gcc-4.2 would be used instead. We can blacklist old clang versions in the port, and I can file a bug report with the developers to see if they want to fix it another way.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign:

I don't see the problem with clang 211 from Xcode 4.2.

Wrong: I do see the problem there.

[ryandesign (Ryan Carsten Schmidt)]

In 02a0091213fac9ffbfdf7419535ee692b52751db/macports-ports:

harfbuzz: Blacklist clang < 300

Closes: #55507