When I emerge evms2, the build created two sym link to two lib files. Specifically libevms and libdlist. However, the link is named without the trailling ".0" while evmsn is looking for the libs with the trailling ".0" Reproducible: Always Steps to Reproduce: 1. emerge evms (in my case v2.2.2) 2. run evmsn (other evms interface should also be affected but I did not try because I don't have X). Actual Results: evmsn fail to execute with error. Expected Results: evmsn execute normally. --- /sbin/ >>> /sbin/evms >>> /sbin/evmsd >>> /sbin/evmsn >>> /sbin/evms_gather_info >>> /sbin/get_dev_num >>> /sbin/evms_activate >>> /lib/libevms.so -> libevms-2.2.so.0.2 >>> /lib/libdlist.so -> libdlist-2.0.so.0.0 * Presently gentoo-sources-2.4.22 has basic support for evms2, * but does NOT support some of the more advanced features. >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... [ ok ] >>> sys-fs/evms-2.2.2 merged. >>> Recording sys-fs/evms in "world" favorites file... >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. meehoon root # meehoon root # evmsn evmsn: error while loading shared libraries: libevms-2.2.so.0: cannot open shared object file: No such file or directory meehoon root # ln -s /lib/libevms-2.2.so.0.2 /lib/libevms-2.2.so.0 meehoon root # evmsn evmsn: error while loading shared libraries: libdlist-2.0.so.0: cannot open shared object file: No such file or directory meehoon root # ln -s libdlist-2.0.so.0.0 libdlist-2.0.so.0 meehoon root # evmsn meehoon root #
The same problem occurs with /etc/init.d/checkfs, when it tries to run evms_activate (a shared library is not found because of a missing link).
Can youu please try 2.3.4
fixed in 2.3.4
I emerge 2.3.4 (while having the previous version installed) and everything went well. So it seems like it's fixed. Thanks.
