Re: (ITS#6517) undefined references to ldif_*

[richm@stanfordalumni.org]

masarati@aero.polimi.it wrote:
>> Michael Ströder wrote:
>>     
>>> hyc@symas.com wrote:
>>>       
>>>> richm@stanfordalumni.org wrote:
>>>>         
>>>>> This is most likely related to my recent LDIF changes.  But I didn't
>>>>> see
>>>>> this problem.  What platform is this?  What build flags are you using?
>>>>>           
>>>> Built fine here too, looks like an inconsistent build tree over there.
>>>>         
>>> The build with the same build flags on the very same system worked right
>>> before the recent libldif check-ins. I'm using anon CVS pserver for cvs
>>> up.
>>>       
>> The anon CVS server has some lag in receiving updates from the master
>> server.
>> Don't you have an account on the master?
>>     
>
> Actually it's not that; Michael routinely builds with --enable-dynamic,
> and libldap now (dynamically) depends on liblutil for the LDIF part.
>   
I did not want to introduce any new dependencies nor break any existing 
code with the new LDIF library.  Ideally, you would only have to link 
with -lldif for external code that wants to use the LDIF API (such as 
ldif_get_entry or ldif_parse_line).  Any existing code, or code that 
just wants to use the new higher level api ldap_parse_ldif_record_x 
would only have to link with -lldap.

Is --enable-dynamic the only additional build flag I need to use?
> p.
>
>
>
>
>
>