swftools-common
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Swftools-common] php calling pdf2swf?


From: Ryan Schmidt
Subject: Re: [Swftools-common] php calling pdf2swf?
Date: Tue, 9 Apr 2013 22:47:28 -0500

On Apr 9, 2013, at 18:02, grimmwerks <address@hidden> wrote:

>  Reason: Incompatible library version: pdf2swf requires version 16.0.0 or 
> later, but libfreetype.6.dylib provides version 15.0.0

This type of error is explained here:

https://trac.macports.org/wiki/ProblemHotlist#libiconv-version

I guess you're not using MacPorts since your prefix is /usr/local, and that 
text talks about libiconv, not libfreetype, but the idea is the same: your 
libfreetype.6.dylib (possibly in /usr/local/lib) is built for the wrong 
architecture, but OS X found another libfreetype.6.dylib elsewhere on your 
system (possibly in /usr/X11/lib) that was the right architecture, but its 
library version is too old. The solution is to install the correct new 
libfreetype.6.dylib for the correct architecture in the right place 
(/usr/local/lib).


> What's strange is it was working fine through terminal...

Sometimes that could be because the $PATH in your terminal is different from 
the default $PATH that php would use, but that's probably not it in your case, 
since you're calling pdf2swf by its absolute path, so we know exactly where it 
is. Instead, I suspect that you've set $DYLD_LIBRARY_PATH or 
$DYLD_FALLBACK_LIBRARY_PATH in your terminal to whatever directory contains the 
correct libfreetype.6.dylib, and the default empty value for those variables 
that php will use is finding a different library.

Run "env" in the terminal to see all the environment variables you've set. If 
DYLD_LIBRARY_PATH or DYLD_FALLBACK_LIBRARY_PATH are there, then we've probably 
found the problem.

Setting DYLD_LIBRARY_PATH in the terminal is a bad idea; it can cause other 
software to fail when it runs with different versions of libraries than the 
ones it was intended to run with. Setting DYLD_FALLBACK_LIBRARY_PATH is less 
bad but should still be avoided. Delete these from your environment; then you 
should see the problem appear on the terminal as well. Then you can work on 
solving the problem correctly, by installing the correctly-built libraries in 
the correct place. Then it should work from php and anywhere else as well.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]