Description:
------------
I'm at my wit's end here. I've spent the last two weeks trying to get PHP to compile correctly. When I set this machine up last spring, I downloaded and installed the latest Apache2 and PHP (4.3.2). I ran it with no problems until early January of this year when I tried to upgrade to PHP 4.3.4 and found that for some reason, even though I'm fairly sure I haven't compiled anything since I built Apache2 and PHP, I could no longer get libphp4.so to come out.

I have tried the following versions of PHP:
4.3.2, 4.3.3, 4.3.4, latest stable, and 4.3.5 RC2

Just for fun, I also tried two versions of Apache2 and the latest version of Apache1.

Reproduce code:
---------------
Here's my config line: (from config.nice)
'./configure' \
'--with-apxs2=/d/apache/bin/apxs' \
'--with-mysql=/d/mysql' \
'--with-config-file-path=/d/apache/conf' \
'--prefix=/d/apache/php' \



Expected result:
----------------
I expected everything to work perfectly, as has always been my experience with PHP. ./configure seemed to work fine (at first, of course) and make works fine, but make install unfailingly yeilds this:


Actual result:
--------------
Warning!  dlname not found in /d/apache/modules/libphp4.la.
Assuming installing a .so rather than a libtool archive.
chmod 755 /d/apache/modules/libphp4.so
chmod: getting attributes of `/d/apache/modules/libphp4.so': No such file or directory
apxs:Error: Command failed with rc=65536
.
make: *** [install-sapi] Error 1

After several attempts, I began to look at the ./configure output and noticed that it's apparently not even attempting to build shared libs.

checking whether the linker (/usr/i386-slackware-linux/bin/ld) supports shared libraries... no
checking how to hardcode library paths into programs... unsupported
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes

It'd be my GUESS (and I'm no guru) that the problem lies here: checking whether the linker (/usr/i386-slackware-linux/bin/ld) supports shared libraries... no

The only problem with that theory is that it's the same ld I was using last time, and it worked just fine then.