php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #10776 Externally set LDFLAGS not exported by configure
Submitted: 2001-05-10 02:34 UTC Modified: 2001-10-23 07:29 UTC
From: d dot begley at uws dot edu dot au Assigned:
Status: Closed Package: Compile Failure
PHP Version: 4.0.5 OS: Solaris 7
Private report: No CVE-ID: None
View Developer Edit
 [2001-05-10 02:34 UTC] d dot begley at uws dot edu dot 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.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-05-18 07:06 UTC] sniper@php.net 
Any examples? Like which libraries are missing?
Which runtime paths?

--Jani
 [2001-05-24 08:43 UTC] d dot begley at uws dot edu dot 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-10-23 07:29 UTC] sniper@php.net 
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
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Mon May 05 20:01:29 2025 UTC