[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: ./configure error

"Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 09/03/04 10:31pm
>I note (for a second time?) that reported mismatch is between
>an old header and new library, suggesting that the problem is
>with the header path not the library path.  I would guess
>that if folks actually looked closer at their environments,
>they would find CPPFLAGS not set, but appropriate flags
>(or other system configuration bits) set in order to
>find the new library.

This may be true in most cases; however, when I ran into the problem
(solaris9), it was definitaly a problem with the runtime location of the
libraries. The thing is that OpenLDAP 2.2.15 (on Sun, I hadn't tried
anything else since 2.1.24) actually tries to execute the binary
produced by the configure script, while before, (again, up to 2.1.24) if
it compiled without error, it was OK. In 2.2.15, the error in my
config.log was from ld.so.1 that libdb-4.2.so was not found. I had
CFLAGS and CPPFLAGS set to look in the proper places and LDFLAGS had
both -L and -R options, and LIBS had the -R options. To solve the
problem, (I do not like to have to set LD_LIBRARY_PATH for each possible
user, nor do I want to use crle for this) I had to set LD_OPTIONS with
the -R path in my parent shell to solve it (it was not enough to set it
in the shell script that executes configure).

I actually prefer this method as it tells me that the configure script
did not pick up my runtime linker flags *before* I compile the entire
package and have to check everything with ldd to make sure that the
runtime information is compiled into the binaries. -- Thanks development


>At 08:03 AM 9/3/2004, Chapman, Kyle wrote:
>>not to push the issue or start a bigger argument, but theres nothing
>>wrong with configuring your system's search path to include the
>>of libraries that your apps need...  dont rely on the app to always
>>how to find the libs.
>>if setting LD_LIBRARY_PATH works, thats great.  if you want to set
>>default search path to include your required lib paths, thats great
>>-----Original Message-----
>>From: owner-openldap-software@OpenLDAP.org 
>>[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of RW
>>Sent: Friday, September 03, 2004 5:51 AM
>>To: openldap-software@OpenLDAP.org 
>>Subject: Re: ./configure error
>>I can confirm this. I've included the BDB lib path in the 
>>LD_LIBRARY_PATH and then configure works fine.
>>This wasn't needed until 2.2.13 (2.2.14 not tested).
>>Armbrust, Daniel C. wrote:
>>> Then what changed in 2.2.15 that makes it not build on my machine -

>>> without setting the LD_LIBRARY_PATH, while 2.2.14 (and all other
>>> versions) build fine without me setting this variable?
>>> And for yet others - it doesn't work when you set all of these

>>> (No one answered him, by the way)
>>> Dan
>>> *From:* Chapman, Kyle [mailto:Kyle_Chapman@G1.com] 
>>> *Sent:* Thursday, September 02, 2004 2:32 PM
>>> *To:* Armbrust, Daniel C.; openldap-software@OpenLDAP.org 
>>> *Subject:* RE: ./configure error
>>> this isnt openldap being broken...
>>> use either -R <path/to/Berkeley> , -rpath <path/to/Berkeley>, crle,

>>> ld.conf, ldconfig, etc... depending on youre os.  -L on aix is 
>>> sufficient to add the path specified to the exe/lib being built.  
>>> these will tell ld where to look for libs at run time.... 
>>NOTICE: This E-mail may contain confidential information. If you are
>>the addressee or the intended recipient please do not read this
>>and please immediately delete this e-mail message and any
>>from your workstation or network mail system. If you are the
>>or the intended recipient and you save or print a copy of this
>>please place it in an appropriate file, depending on whether
>>confidential information is contained in the message.