Bug 316 - libgdiplus.dylib is missing _DGifOpen
Summary: libgdiplus.dylib is missing _DGifOpen
Alias: None
Product: Runtime
Classification: Mono
Component: packaging ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Alex Corrado [MSFT]
Depends on:
Reported: 2011-08-17 16:54 UTC by Jeremiah Boyle
Modified: 2011-09-02 13:04 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Jeremiah Boyle 2011-08-17 16:54:56 UTC
the libgdiplus.dylib included with 2.10.4 seems broken or at least missing gif support. it is, notably, half as large as the library included with 2.10.2.

my app is complaining:

dyld: lazy symbol binding failed: Symbol not found: _DGifOpen
  Referenced from: /Library/Frameworks/Mono.framework/Versions/2.10.4/lib/libgdiplus.dylib
  Expected in: flat namespace

if i sub in the library from 2.10.2, everything works as expected.
Comment 1 Alex Corrado [MSFT] 2011-08-18 17:45:31 UTC
It looks like a 64-bit version of giflib was being used accidentally. This will be fixed in the next mono release. For now, subbing in the 2.10.2 libgdiplus is the best workaround.
Comment 2 Jeremiah Boyle 2011-08-31 13:40:39 UTC
this appears to be fixed in 2.10.5.
Comment 3 Alex Corrado [MSFT] 2011-09-02 13:04:20 UTC
Yes, this should be fixed in 2.10.5. Thanks, Jeremiah.