[Xfce-bugs] [XFCE 0000241]: CVS build - ldconfig does not recognize libxfce4mcs- client or manager

[xfce-bugs at xfce.org]

The following bug has been RESOLVED.
=======================================================================
http://bugs.xfce.org/view_bug_page.php?f_id=0000241
=======================================================================
Reporter:                   elherr
Handler:                    huysmans
=======================================================================
Project:                    XFCE
Bug ID:                     0000241
Category:                   general
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Resolution:                 fixed
=======================================================================
Date Submitted:             2004-06-25 11:38 GMT
Last Modified:              2004-08-19 19:56 GMT
=======================================================================
Summary:                    CVS build - ldconfig does not recognize libxfce4mcs- client or manager
Description: 
After building from CVS (2004-6-24) ldconfig (Debian unstable) does not
recognize libxfce4mcs-client.0.2.0 and libxfce4mcs-manager.0.2.0 . It
appears ldconfig will not accept any shared lib files without ".so" in the
name.

ldconfig version:
eherr at hermes:~$ ldconfig -V
ldconfig (GNU libc) 2.3.2

A workaround is to: 
1. rename the libraries as (adding .so)...
libxfce4mcs-client.so.0.2.0
libxfce4mcs-manager.so.0.2.0

2. Rebuild symlinks to
libxfce4mcs-client -> libxfce4mcs-client.so.0.2.0
libxfce4mcs-manager -> libxfce4mcs-manager.so.0.2.0

3. Run ldconfig

=======================================================================

-----------------------------------------------------------------------
 huysmans - 2004-07-15 07:46 GMT 
-----------------------------------------------------------------------
This is a libtool error. Running autogen.sh instead of configure should fix
it.

Can it be someone committed some broken libtool stuff to CVS? We seem to
be getting more of these reports again, lately.

-----------------------------------------------------------------------
 kelnos - 2004-07-19 21:02 GMT 
-----------------------------------------------------------------------
i have a suspicion that it's not the different versions we all seem to be
using, but that some trees have a _mix_ of versions.  i'm guilty of this
too, but whenever anyone changes anything that messes with even _one_ of
the autogenerated files, they _all_ should be committed back to cvs.

-----------------------------------------------------------------------
 huysmans - 2004-08-19 19:56 GMT 
-----------------------------------------------------------------------
I believe this is fixed, since we didn't hear any more complaints for a
while. Please reopen if there still is a problem.