BUG: jpeg-6b dylib conflicts with ApplicationServices

[cssdev@…]

I installed jpeg-6b on Mac OS X 10.4, and its presence in /opt/local/lib appears to conflict severely with ApplicationServices. With the dylib in place, the 'open' command fails with the following error:

$ open .
dyld: Symbol not found: __cg_jpeg_resync_to_restart
  Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/
Frameworks/ImageIO.framework/Versions/A/ImageIO
  Expected in: /opt/local/lib/libJPEG.dylib

Trace/BPT trap

There is a CrashReporter log, but it pretty much duplicates the same information:

Link (dyld) error:

Symbol not found: __cg_jpeg_resync_to_restart
  Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/
Frameworks/ImageIO.framework/Versions/A/ImageIO
  Expected in: /opt/local/lib/libJPEG.dylib

My drive is formatted using case-insensitive HFS+, so it appears that might be a conflict with the existing image libraries. I haven't figured out a workaround yet, so for now I have deactivated the ports on my machine. A search on Google turned up someone who had the same problem with mono, but the conflict resulted in an inabiltiy to log into his computer! <​http://lists.ximian.com/archives/public/ mono-osx/2005-May/000120.html>

Should ports now hook into the ImageIO framework? Is this a MacOS bug that should be reported to prevent conflicts?

[voorhees@…]

I also have a problem with the jpeg package.

mine occurs when tryinging to start apache w/ php +gd

Syntax error on line 275 of /opt/local/apache2/conf/httpd.conf: Cannot load /opt/local/apache2/modules/libphp5.so into server: Symbol not found: cg_jpeg_resync_to_restart\n Referenced from: /System/Library/Frameworks/ ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO\n Expected in: /opt/local/lib/libjpeg.62.dylib\n

anyone know what's going on? is their a work around?

-Will

[marcin@…]

I also get exactly the same error as #1 after installing php4 +macosx +mysql4 +apache2. I've made sure darwinports is up to date and also tried to upgrade the "jpeg" package, with no success.

[brian@…]

This is related to bug 3042. For apache2, I commented out the lines that set DYLD_LIBRARY_PATH in / opt/local/apache2/bin/envvars to get apache to start with the php module.

[bchesneau@…]

(In reply to comment #3)

This is related to bug 3042. For apache2, I commented out the lines that set

DYLD_LIBRARY_PATH in /

opt/local/apache2/bin/envvars to get apache to start with the php module.

works for me too.

[cssdev@…]

If I use DYLD_FALLBACK_LIBRARY_PATH instead, then things continue without causing a crash. This approach preserves my ability to use code that still relies on a dynamic library path.

[jberry@…]

Changed apache2 to set DYLD_FALLBACK_LIBRARY_PATH instead of DYLD_LIBRARY_PATH. Marking bug as fixed. Please verify.

[scott@…]

Am I missing the solution to solve this as I cannot use 'open' now as well.

Just looking for the solution.

(In reply to comment #0)

I installed jpeg-6b on Mac OS X 10.4, and its presence in /opt/local/lib appears to conflict severely with ApplicationServices. With the dylib in place, the 'open' command fails with the following error:

$ open . dyld: Symbol not found: cg_jpeg_resync_to_restart

Referenced from:

/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ Frameworks/ImageIO.framework/Versions/A/ImageIO

Expected in: /opt/local/lib/libJPEG.dylib

Trace/BPT trap

There is a CrashReporter log, but it pretty much duplicates the same information:

Link (dyld) error:

Symbol not found: cg_jpeg_resync_to_restart

Referenced from:

/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ Frameworks/ImageIO.framework/Versions/A/ImageIO

Expected in: /opt/local/lib/libJPEG.dylib

My drive is formatted using case-insensitive HFS+, so it appears that might be a conflict with the existing image libraries. I haven't figured out a workaround yet, so for now I have deactivated the ports on my machine. A search on Google turned up someone who had the same problem with mono, but the conflict resulted in an inabiltiy to log into his computer! <​http://lists.ximian.com/archives/public/ mono-osx/2005-May/000120.html>

Should ports now hook into the ImageIO framework? Is this a MacOS bug that should be reported to prevent conflicts?

[jameskyle@…]

Why is it necessary to set the DYLD path for apache2?

[jameskyle@…]

Cc Me!