Configure generates wrong Makefile for PHP.

[jonathan@…]

The error is in the version 3.5 and 3.6.

When I run the configure, everything go cool, but, when I run make, the error 
occurs:

# make

gcc -shared -L/usr/local/lib -rdynamic-Wl -o php_mapscript.so 
php_mapscript_util.o php_mapscript.o mapscript_i.o  
-L/root/Mapserver-novo/mapserver-3.6.6 -lmap -L/usr/local/lib -lwwwxml -lxmltok 
-lxmlparse -lwwwinit -lwwwapp -lwwwhtml -lwwwtelnet
-lwwwnews -lwwwhttp -lwwwmime -lwwwgopher -lwwwftp -lwwwfile -lwwwdir -lwwwcache 
-lwwwstream -lwwwmux -lwwwtrans -lwwwcore
-lwwwutils -lmd5 -ldl -L/usr/local/pgsql/lib -lpq  -L/usr/local/lib -lgdal.1.1   
 -L/root/mapserver/proj-4.4.7/src/.libs -lproj -ltiff -L/root/mapserver/jpeg-6b/ 
-ljpeg -lfreetype -L/root/mapserver/libpng-1.2.5 -lpng -L/root/mapserver/zlib-1.
1.4
-lz   -L/root/mapserver/jpeg-6b/ -ljpeg -lfreetype -L/root/mapserver/libpng-1.2.
5 -lpng -L/root/mapserver/zlib-1.1.4 -lz -L/root/mapserver/jpeg-6b/ -ljpeg   -lm 
-lstdc++ /root/mapserver/gd-2.0.12/.libs/libgd.a
gcc: unrecognized option `-rdynamic-Wl'
make[1]: Saindo do diretório `/root/Mapserver-novo/mapserver-3.6.
6/mapscript/php3'

The option of gcc, -rdynamic-Wl, doesn't exist, is -rdynamic -Wl, so: 

# grep -i "rdynamic" * -R
config.status:s%@PHP_LD@%gcc -shared -L/usr/local/lib -rdynamic-Wl%g
mapscript/php3/Makefile:LD =     gcc -shared -L/usr/local/lib -rdynamic-Wl

# sed s/-rdynamic-Wl/-rdynamic\ -Wl/g mapscript/php3/Makefile > 
mapscript/php3/Makefile.new && cp mapscript/php3/Makefile.new 
mapscript/php3/Makefile -f

# make clean ; make

[]'s

[dmorissette]

Can you try adding --enable-internal-ld-detect to your configure options with 
version 3.6.  This will trigger the use of a new macro for the php_mapscript.so 
linking parameters that fixes several issues of this type, this new macro is 
used by default in version 4.0.

I'll mark this bug as WONTFIX since we won't be releasing any more 3.6.x 
versions and I believe this configure option should solve your problem for 3.6.  
Also since this new option is the default for 4.0 then this problem should not 
be an issue any more in 4.0.

If you can reproduce the same issue with 4.0 then please reopen the bug.