[MacPorts] #48024: charm-qt5 @1.8.0_20150312: cannot evaluate portfile

René J.V. Bertin rjvbertin at gmail.com
Fri Jun 19 01:55:47 PDT 2015


Trac  seems to be down ATM, so to avoid losing the reply I just typed I'm copying it via email.
(indeed, data.macosforge.org isn't replying, according to the majestic Python *2.6* backtrace I just obtained in my browser)

Replying to [comment:19 mk@…]:
> Finally I was - in a 1st step - able to update the current qt5-mac on my VM. That left me puzzled, as it suddenly needs the {{{x11}}} variant for {{{pulseaudio}}} per default. Is that a bug or intended?

I'd call it an intended bug ;) It's simply because mainstream qt5-mac is configured to use pulseaudio (PA) because that'd be the default *if PA is installed*. Evidently someone only interested in Qt and KDE applications (probably) won't have that port installed, so it and its dependencies are pulled in.

> Rebuilding {{{charm}}} in the process succeeded, but it crashes when run:
> {{{
> Dyld Error Message:
>   Library not loaded: /opt/local/Library/Frameworks/QtCore.framework/Versions/5/QtCore
>   Referenced from: /Applications/Charm.app/Contents/MacOS/Charm
>   Reason: image not found
> }}}

That shouldn't happen with either version of the co-installable Qt5 port: it's looking for the QtCore framework in its old, "exclusive" location. This error could arise when you forgot to install charm after building it, or if for some reason the previous version got re-activated.
It's of course possible too that the charm Portfile does things in the post-destroot that cause this error, which would IMHO suggest an issue with the mainstream Qt5 PortGroup.

I'm a bit surprised also by charm's install location: I'm pretty sure that my initial port proposition had it install to `/Applications/MacPorts/Qt{4,5}`, not to /Applications. Did you change that?


More information about the macports-dev mailing list