Re: PHP_SHLIB_SUFFIX not being properly set on MacOSX

brad@laptop ~ $ autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. brad@laptop ~ $ automake --version automake (GNU automake) 1.9.3 Written by Tom Tromey <tromey@redhat.com>. Copyright 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. brad@laptop ~ $ libtool --version ltmain.sh (GNU libtool) 1.5.10 (1.1220.2.131 2004/09/19 12:46:56) Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I just ran phpize which gave no errors, then ./configure make make install make distclean on a Linux box then tarred it up, and sent it to my MacOSX box, and ./configure barfed on an OpenSSL detection because it was looking for libssl.so and libcrypto.so instead of libssl.dylib and libcrypto.dylib. config.log _clearly_ showed that host_alias was blank. -Brad Jani Taskinen wrote:

    How exactly did you run the phpize and the generated configure?
    What are the autoconf, libtool and automake versions in your system?

    Checking configure generated on my machine, it's impossible
    for $host_alias to be empty unless you specify it to be
    empty with --host="" or something like that.

    I wouldn't want to fix something that really isn't broken. :)

    --Jani

On Tue, 4 Jan 2005, Brad House wrote:

Just tried to phpize an extension, and it appears as though there is a problem on MacOSX. PHP_SHLIB_SUFFIX defaults to .so because a check is run on $host_alias, which is set to "". Attached is a patch to use $host_os instead which fixes the problem. This is against php-4.3.10 by the way. I have not confirmed if PHP 5 has this issue or not. -Brad