The libso target builds libutil.so . This name conflicts with libutil.so from glibc .
This prohibits the natural (for me) way of installing the library: put libs in /usr/local/lib64/cudd/,
then put a file pointing to that directory in /etc/ld.so.conf.d/, then run ldconfig. This avoids setting LD_LIBRARY_PATH.
I am not sure how this type of situation should be handled. I guess the name should be libcudd_util.so, and similarly for the other libs. But why does it have to be 6 separate libs? Perhaps they can be merged into one (libcudd)? (Cf. http://stackoverflow.com/questions/915128/merge-multiple-so-shared-libraries )
Fedora packages cudd and has renamed util (and st):
rpm -ql cudd|grep so..\$
/usr/lib64/libcudd.so.2
/usr/lib64/libcuddobj.so.2
/usr/lib64/libcuddst.so.2
/usr/lib64/libcuddutil.so.2
/usr/lib64/libdddmp.so.2
/usr/lib64/libepd.so.2
/usr/lib64/libmtr.so.2
To use this with haskell_cudd, these names should go in the cabal file, see other issue.
The
libsotarget buildslibutil.so. This name conflicts withlibutil.sofromglibc.This prohibits the natural (for me) way of installing the library: put libs in
/usr/local/lib64/cudd/,then put a file pointing to that directory in
/etc/ld.so.conf.d/, then runldconfig. This avoids settingLD_LIBRARY_PATH.I am not sure how this type of situation should be handled. I guess the name should be
libcudd_util.so, and similarly for the other libs. But why does it have to be 6 separate libs? Perhaps they can be merged into one (libcudd)? (Cf. http://stackoverflow.com/questions/915128/merge-multiple-so-shared-libraries )Fedora packages cudd and has renamed util (and st):
To use this with haskell_cudd, these names should go in the cabal file, see other issue.