[MacPorts] #3013: BUG: jpeg-6b dylib conflicts with ApplicationServices

[MacPorts]

#3013: BUG: jpeg-6b dylib conflicts with ApplicationServices
-----------------------------+----------------------------------------------
  Reporter:  cssdev@…        |       Owner:  waqar@…           
      Type:  defect          |      Status:  closed            
  Priority:  Normal          |   Milestone:                    
 Component:  ports           |     Version:  1.0               
Resolution:  fixed           |    Keywords:                    
      Port:                  |  
-----------------------------+----------------------------------------------

Old description:

> 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?

New description:

 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?

--

Comment(by jameskyle@…):

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

-- 
Ticket URL: <http://trac.macports.org/ticket/3013#comment:10>
MacPorts <http://www.macports.org/>
Ports system for Mac OS