Opened 11 years ago
Last modified 10 years ago
#39598 closed defect
webkit-gtk: Symbol not found: __cg_jpeg_resync_to_restart — at Version 1
Reported by: | drs@… | Owned by: | jeremyhu@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | devans@… | |
Port: | harfbuzz-icu webkit-gtk |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
My os/architecture information is:
Darwin XX.local 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64
When attempting to upgrade via 'port upgrade outdated
', I find that upgrading webkit-gtk to 2.0.3 fails with:
:info:build clang: warning: argument unused during compilation: '-pthread' :info:build dyld: Symbol not found: __cg_jpeg_resync_to_restart :info:build Referenced from: /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO :info:build Expected in: /opt/local/lib/libjpeg.9.dylib :info:build in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
I find that reverting to "webkit-gtk @2.0.1_0+quartz+video" resolves the issue. No other changes were made to environment or macports state other than moving the Portfile for webkit-gtk back to the 2.0.1_0 version with the dependency updated to 'port:harfbuzz-icu'.
Note that neither DYLD_LIBRARY_PATH nor DYLD_FALLBACK_LIBRARY_PATH is present in my environment.
I will attach the build log and the modified Portfile.
Change History (3)
Changed 11 years ago by drs@…
Changed 11 years ago by drs@…
Attachment: | webkit-gtk.error-log.txt.gz added |
---|
log file with error from attempted update
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | devans@… added |
---|---|
Description: | modified (diff) |
Owner: | changed from macports-tickets@… to jeremyhu@… |
Note that neither DYLD_LIBRARY_PATH nor DYLD_FALLBACK_LIBRARY_PATH is present in my environment.
MacPorts does not use your environment when it's running. It uses its own sanitized environment, controlled from macports.conf.
I can't think of a reason for this to be happening, other than the one you already ruled out.
reverted 2.0.1_0 portfile