NYCPHP Meetup

[William Klein]

> The ./configure script keeps a config.log in current directory of all
> of the tests it's tried. Usually the tests involve dynamically
> creating a small test program and then trying to compile it. If that
> compilation failed, you should see the compiler error. It could be
> just a missing dependency that the vendor didn't anticipate or it
> could be that PHP uses a specific API that isn't present in the
> library you want to use.

Excellent advice, thank you, that told me quite a bit.  The relevant log
entrys are:

configure:32582: checking for FDF support
configure:32800: checking for FDFOpen in -lFdfTk
configure:32819: gcc -o conftest -g -O2  -Wl,-rpath,/usr//lib -L/usr//lib
-lm conftest.c -lFdfTk  -lresolv -lm -ldl -lnsl  -lxml2 -lz -lm -lxml2 -lz
-lm 1>&5
/usr/bin/ld: skipping incompatible /usr//lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr//lib/libm.a when searching for -lm
/usr/bin/ld: skipping incompatible /usr//lib/libFdfTk.so when searching for
-lFdfTk
/usr/bin/ld: skipping incompatible
/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../libFdfTk.so when searching
for -lFdfTk
/usr/bin/ld: skipping incompatible /usr/local/lib/libFdfTk.so when searching
for -lFdfTk
/usr/bin/ld: skipping incompatible /usr/lib/libFdfTk.so when searching for
-lFdfTk
/usr/bin/ld: cannot find -lFdfTk
collect2: ld returned 1 exit status
configure: failed program was:
#line 32808 "configure"

So a bit of googling and I find this usually means there are 32 bit
libraries that are for some reason incompatible with 64 bit libraries.  The
things I've read say link the incompatible libraries to their 64 bit
versions.  Since the Adobe toolkit is distributed in binary form, I'm
guessing it's 32 bit, I'm not sure how to get around it.  I don't
particularly want to reformat the server with a 32 bit OS.  I'm thinking the
difference between a 64 and 32 bit version is minimal.  Is there a way of
forcing php to compile in 32 bit mode?