Opened 7 years ago
Closed 7 years ago
#55507 closed defect (fixed)
port upgrade harfbuzz 1.4.5 to 1.7.2_0 fails
Reported by: | tomemm | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.2 |
Keywords: | lion | Cc: | nerdling (Jeremy Lavergne) |
Port: | harfbuzz |
Description
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.
Attachments (2)
Change History (11)
Changed 7 years ago by tomemm
Attachment: | harfbuzzmain1.log added |
---|
comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | lion added; upgrade harfuzz removed |
---|---|
Owner: | set to ryandesign |
Port: | harfbuzz added |
Status: | new → assigned |
comment:2 Changed 7 years ago by nerdling (Jeremy Lavergne)
Cc: | nerdling added |
---|
comment:4 Changed 7 years ago by 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
comment:5 Changed 7 years ago by 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?
Changed 7 years ago by nerdling (Jeremy Lavergne)
Attachment: | harfbuzz-55507.tbz2 added |
---|
cannot initialize a parameter of type 'volatile long long *' with an rvalue of type 'OT::post::accelerator_t '
comment:6 Changed 7 years ago by 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 **'
comment:7 follow-up: 8 Changed 7 years ago by 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.
comment:8 Changed 7 years ago by 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.
comment:9 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Huh.
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.