Bug #10776 Updated: Externally set LDFLAGS not exported by configure

ID: 10776 Updated by: sniper Reported By: d.begley@uws.edu.au Old Status: Open Status: Closed Bug Type: Compile Failure Operating System: Solaris 7 PHP Version: 4.0.5 New Comment: With latest CVS these flags should not be needed. LDAP configure should detect and add them by itself. Please try latest CVS snapshot from http://snaps.php.net/ and reopen if it doesn't work for you. --Jani Previous Comments: ------------------------------------------------------------------------ [2001-05-24 08:43:44] d.begley@uws.edu.au A simple example would be: LDFLAGS="-s -L/opt/NCCldapsdk/lib -R/opt/NCCldapsdk/lib -lnspr3 -lplc3 -lplds3" export LDFLAGS ./configure ... LDFLAGS in this case will be used for the duration of "configure" (for example compile tests), but the contents of LDFLAGS are not passed through to the rest of the build process. See "config.status" for example - CFLAGS is there but the contents of LDFLAGS is blank. In "configure" itself, there's a SUBST for CFLAGS (and others) but none for LDFLAGS. ------------------------------------------------------------------------ [2001-05-18 07:06:00] sniper@php.net Any examples? Like which libraries are missing? Which runtime paths? --Jani ------------------------------------------------------------------------ [2001-05-10 02:34:53] d.begley@uws.edu.au If you set CC, CFLAGS and LDFLAGS prior to running configure, CC and CFLAGS will be used by and exported through configure such that it works for the remainder of the build - but LDFLAGS is only used by configure (then ignored, not exported to the remaining build scripts). This causes some runtime paths and libraries to be missing from the resultant PHP binary, leading to execution failure. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=10776&edit=1