https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7152
--- Comment #1 from Guy Harris <guy@xxxxxxxxxxxx> 2012-04-19 14:19:08 PDT ---
(You can get the build information from the command line by running Wireshark
from the command line with the -v option.)
libfreetype is coming from the OS's X11, so I'm not sure an update of freetype
from macports will help.
I'm running 10.6.8 on my MacBook Pro, and its libfreetype is 14.0.0:
$ otool -L /usr/X11/lib/libfreetype.6.dylib
/usr/X11/lib/libfreetype.6.dylib:
/usr/X11/lib/libfreetype.6.dylib (compatibility version 14.0.0, current
version 14.2.0)
If you installed the 64-bit Snow Leopard dmg from wireshark.org, then:
If you're running a pre-10.6.8 version of Snow Leopard, updating to 10.6.8
might get you an up-to-date libfreetype.
If you're running 10.6.8, and it hasn't had all of the security updates
applied, *perhaps* applying them all would update it.
If you installed the 32-bit Leopard dmg (which you should only do if you have a
32-bit machine, i.e. one with an Intel Core Solo or Intel Core Duo, *not* with
a Core 2 or Core i3/i5/i7), there might be an issue with the way GNU libtool
does library versioning.
The underlying problem is probably that we're not building against the SDK, but
are building against the libraries installed on the system, which can cause
problems with OS versions older than the one running on the buildbot. See bug
5937; if that's the problem here, this is a duplicate of that.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.