I just uploaded 2.7.4_beta2 which addresses this linking issue, and my build script now checks for issues like this, so if something like this happens again, it will be caught before releasing a build. Thanks, Jeremy On Aug 30, 2012, at 22:53, Jeremy Huddleston Sequoia <jeremyhu@apple.com> wrote:
Sigh. Thanks for pointing this out.
I need to create a post-build phase which will sanity check the binaries to ensure that /opt/local and /usr/local libs don't get linked in.
I'm going to pull the update. Sorry for the inconvenience.
--Jeremy
On Aug 30, 2012, at 10:42, SciFi <sci-fi@hush.ai> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I've been using XQuartz-2.7.3 fine (for my simple purposes).
I got this during the install of XQuartz-2.7.4_beta1: […] installer[68580]: PackageKit: Executing script "./postinstall" in /private/tmp/PKInstallSandbox.Pf4b10/Scripts/org.macosforge.xquartz.pkg.jjrTaV installer[68580]: ./postinstall: lockfile: Forcing lock on "/opt/X11/var/run/font_cache.lock" installer[68580]: ./postinstall: font_cache: Scanning system font directories to generate X11 font caches installer[68580]: ./postinstall: font_cache: Making fonts.dir for updated directories. […] installer[68580]: ./postinstall: font_cache: Updating FC cache installer[68580]: ./postinstall: dyld: Library not loaded: /usr/local/lib/libexpat.1.dylib installer[68580]: ./postinstall: Referenced from: /opt/X11/bin/fc-cache installer[68580]: ./postinstall: Reason: Incompatible library version: fc-cache requires version 8.0.0 or later, but libexpat.1.dylib provides version 7.0.0 installer[68580]: ./postinstall: /opt/X11/bin/font_cache: line 122: 71623 Trace/BPT trap ${X11DIR}/bin/fc-cache -s $([[ $force == 1 ]] && echo "-f -r") $([[ $verbose == 1 ]] && echo "-v") installer[68580]: ./postinstall: font_cache: Done installer[68580]: PackageKit: Registered bundle file://localhost/Applications/Utilities/XQuartz.app/ […]
It seemed to finish installing, however, so I launched the new XQuartz.app, which did not give an xterm window as it had the same problem with the new libfontconfig and existing libexpat.
Indeed my build of Pan again had the same problem with libfontconfig and libexpat.
I went back to XQuartz-2.7.3 (reinstalling it) and things seem fine again. ;)
I'm kinda afraid to update expat myself, it seems to be needed way-deep in the chain for too many projects I would then need to rebuild.
FWIW -- I must stay with running 10.6.8 with all official updates etc. on a "iMac6,1" model (I build by hand using Xcode-3.2.6 almost all open-source code I use).
Thanks for trying to keep us updated.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJQP6T/AAoJEKkeWNKet7+KYfcH/jMBZFEvJSWR4v0pTEcXGSL5 FJZH2YHHuBSvhhZ/fU4y6s3hdNk0tZrmm2gmx4bmTJZBtViOxrVuYxlB0AsFrqhi gRpZizCRqpEAK7MxiSaOYNOMznMceet32nC28D1tLa0H18huz07B0pNPrSwxRPYa K41bkCE3ZcEPy2huh4S4OsWrp2byiWstGovm7VlVpJfVUDK+jbNj1AQbpyo/t/Vs o0QIk50YwG2NTYplXgvHmvoCnfgZEdFLWWUO3RWF7HwE7llCImZCmdTkhcZKNel2 h/ceWvJMk9sP6fb5dG5/3AXIgl57iWXq2sVpmMSoVhDmUiu7slike67d3qT8wxU= =fHwa -----END PGP SIGNATURE-----
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev