bzr-svn on Solaris 10

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Harald Meland wrote:
> [Russel Winder]

...

>> |> ldd /home/users/russel/.bazaar/plugins_SunOS_sparc/svn/*.so | grep
>> libresolv
>>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
>>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
>>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
>>         libresolv.so.2 =>        /usr/lib/libresolv.so.2
>>         libresolv.so.2 (SUNW_2.2.2) =>   (version not found)
>> |> 
>>
>> It seems not. :-(
> 
> If you run the same command, but without the grep, you can see which
> of the svn plugin's .so files are having troubles resolving
> libresolv.so.2.  Could it be that you have some old ones still lying
> around?
> 
>> I am guessing the SUNW_2.2.2 is the problem here. I guess I am going
>> to have to back out all the Neon/Subversion upgrades.
> 
> Yeah, I'd guess that one of the libraries the svn plugin links against
> have in turn been linked again version SUNW_2.2.2 of the resolver
> library; unless you've upgraded the resolver library recently, your
> recent Neon/Subversion update seems a likely culprit.
> 
> You could run ldd on binaries/libraries from those updated packages to
> verify which one(s) are giving you trouble, and see if there are
> further upgrades available to fix that.

Another thing to check. Are you sure that all of the files got rebuilt
and re-linked after the upgrade? Deleting them all and building from
scratch may prove useful.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkqueAACgkQJdeBCYSNAAOe9QCdH5cjTqPe9PjEJGhe5uCklksX
aCEAnihY3Lb2hGP2gmZxlUszbPuvC2Zx
=/TAM
-----END PGP SIGNATURE-----