Don't try outsmarting the configure. User error -> not PHP bug.

Whoah! Please don't be misled by the configure script I submitted in this bug report - the LDFLAGS and CPPFLAGS variables were set during my attempts to work around the problem because I originally thought that the build was picking up the wrong libtcl.so. I have since verified that the only copies of this library on my system are under the Sybase paths.

It does appear that the wrong libintl.so library is being picked up - it should be using the one under the Sybase path, but is ignoring it and using the one under /usr/lib instead.

I have tried this build against both the Sybase 12.0 and 12.5 client libraries with identical results.

My original configure script is:

#!/usr/bin/sh

DSQUERY=fx_dbserver2_ds
SYBASE=/dpkg/sybase/sybase12_5
SYBASE_OCS=OCS-12_5
LD_LIBRARY_PATH=$SYBASE/$SYBASE_OCS/lib:/usr/local/lib:$LD_LIBRARY_PATH
PATH=/usr/ccs/bin:$PATH

export DSQUERY SYBASE SYBASE_OCS LD_LIBRARY_PATH PATH

cd php-5.0.5

./configure \
  --prefix=/usr/local/php \
  --with-apxs2=/usr/local/apache2/bin/apxs \
  --with-sybase-ct=$SYBASE/$SYBASE_OCS \
  --without-bz2

This produces a libphp5.so which is linked as follows:

ldd /usr/local/apache2/modules/libphp5.so
        libtcl.so =>     /dpkg/sybase/sybase12_5/OCS-12_5/lib/libtcl.so
        libintl.so.1 =>  /usr/lib/libintl.so.1
        libcomn.so =>    /dpkg/sybase/sybase12_5/OCS-12_5/lib/libcomn.so
        libct.so =>      /dpkg/sybase/sybase12_5/OCS-12_5/lib/libct.so
        libcs.so =>      /dpkg/sybase/sybase12_5/OCS-12_5/lib/libcs.so
        libresolv.so.2 =>        /usr/lib/libresolv.so.2
        libm.so.1 =>     /usr/lib/libm.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libz.so.1 =>     /usr/lib/libz.so.1
        libxml2.so.2 =>  /usr/local/lib/libxml2.so.2
        libiconv.so.2 =>         /usr/local/lib/libiconv.so.2
        libc.so.1 =>     /usr/lib/libc.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        libpthread.so.1 =>       /usr/lib/libpthread.so.1
        libgcc_s.so.1 =>         /usr/local/lib/libgcc_s.so.1
        /usr/platform/SUNW,Ultra-80/lib/libc_psr.so.1
        libthread.so.1 =>        /usr/lib/libthread.so.1


NOTE that the reference to libintl is still linked to the wrong library.

I have investigated further and found that libintl.so.1 doesn't exist under the Sybase path - only libintl.so is found there. I need to somehow force the build to pick up the Sybase library instead of the Solaris library.

A solved case on the Sybase site mentions that the Solaris library /usr/lib/libintl.so.1 has nothing to do with the Sybase library of the same name, which is possibly why the object not found error since my build is linking to the wrong library!

I have managed to get around the build problem by sym-linking libintl.so -> libintl.so.1 in the Sybase libraries path. Apache2 now starts with the php5 module configured.

This seems to me to be an issue with the PHP build - we have no such problems compiling other CTLIB applications!

Please note - the 'duplicate' name of the libintl library is NOT Sybase's problem. Sybase support say that they created that library 'years' before Solaris introduced one of the same name.

Bittersweet victory though, because now sybase_connect() won't connect despite the interfaces file being present, correct and configured in php.ini.

Just another thing to note: The following message appears during 'make install' ...

"libtool: install: warning: remember to run `libtool --finish /var/build/php-5.0.5/libs'"

I would expect to see the message ...

----------------------------------------------------------------------
Libraries have been installed in:
   /var/build/php-5.0.5/libs

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - use the `-RLIBDIR' linker flag

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------

... during the install phase, but this is missing. I presume this is purely informational?

Sorry - I know this is unrelated to the above, just thought I should bring it to your attention.

This still isn't PHP bug.

No, perhaps not a bug with PHP itself, but definitely an issue with the build process!!

You telling me you're just going to leave Solaris users who need Sybase support swinging in the breeze?

I strongly suspect the problem is to do with GCC - which uses the non-Sybase version of the libintl library, but haven't had time to investigate further.