Hi,
If you check the library version information:
pvs /usr/lib/libresolv.so.2
you should see a list of version information. On my s10u7 and s10u8
machines I get:
$ pvs /usr/lib/libresolv.so.2
libsocket.so.1 (SUNW_1.4, SUNWprivate_1.1);
libnsl.so.1 (SUNW_1.9.1, SUNWprivate_1.4);
libc.so.1 (SUNW_1.22, SUNWprivate_1.1);
libresolv.so.2;
SUNW_2.2.2;
SUNW_2.2.1;
SUNW_2.2;
SUNW_2.1;
SUNWprivate_2.2;
SUNWprivate_2.1;
There's a couple of possibilities. Perhaps your dev machine has an
earlier s10 installation and has an earlier version of libresolv.so.2,
and hence there's a mismatch between what the ldap shared library svn
uses needs to link with and what your box makes available. Or there are
multiple versions of svn available in different directories and the
maven plugin isn't running the same one that you are from the command line.
Regards,
Steve
Ed Burns wrote:
> Hello Team,
>
> My on-SWAN dev machine, running solaris 10 X86 is having problems with
> svn.
>
> When I try to run svn on jsfci.sfbay.sun.com, I get
>
> ld.so.1: svn: fatal: libresolv.so.2: version `SUNW_2.2.2' not found (required by file /usr/local/lib/libldap-2.4.so.2)
> ld.so.1: svn: fatal: libresolv.so.2: open failed: No such file or directory
> Killed
>
> Oddly, this hasn't been a problem for the mvn-scm-plugin. It seems to
> be able to run svn just fine. It's only when I ant exec svn (as Jane is
> doing in the source-build area) that I get this error. I searched the
> web for solutions but didn't find anything conclusive.
>
> I've been working around this by running svn on the sunray, writing
> files to the solaris 10 X86 machine via nfs. This workaround doesn't
> work in the case of Jane's source-build because the same ant file both
> checks out and builds the source.
>
> This is not urgent since I can use my off-SWAN machine but due to the
> size of the source-build repo, I prefer to do it on-SWAN.
>
> If anyone can help, I'd really appreciate it.
>
> Thanks,
>
> Ed
>
>