James Pifer wrote: >> As root, edit a file with a name that makes sense in /etc/ld.so.conf.d >> on the order of app-name.conf. In that file place the pathname to the >> libraries of the application. (Take a look at existing files). >> >> Then run ldconfig. >> >> Ed >> > > Not having much luck. I created a file called: > /etc/ld.so.conf.d/arlibs.conf > > It contains this path: > /usr/local/lib/ar63 > > When I run ldconfig I get: > # ldconfig > ldconfig: /usr/local/lib/ar63/libicutoolutil28.so.28 is not a symbolic link > > ldconfig: /usr/local/lib/ar63/libicuio28.so.28 is not a symbolic link > > ldconfig: /usr/local/lib/ar63/libicui18n28.so.28 is not a symbolic link > > ldconfig: /usr/local/lib/ar63/libicule28.so.28 is not a symbolic link > > ldconfig: /usr/local/lib/ar63/libiculx28.so.28 is not a symbolic link > > ldconfig: /usr/local/lib/ar63/libicudata28.so.28 is not a symbolic link > > ldconfig: /usr/local/lib/ar63/libicuuc28.so.28 is not a symbolic link > > > The files in /usr/local/lib/ar63 are: > ls -l > total 49100 > -rwxr-xr-x 1 root root 3202324 May 17 08:17 libar.a > -rwxr-xr-x 1 root root 4060096 May 17 08:18 libarjni63.so > -rwxr-xr-x 1 root root 2445439 May 17 08:19 libar.so > -rwxr-xr-x 1 root root 376230 May 17 08:19 libarutiljni63.so > -rwxr-xr-x 1 root root 5964473 May 17 08:21 libarxmlutil.so > -rw-r--r-- 1 root root 8278341 May 17 08:23 libicudata28.so > -rw-r--r-- 1 root root 8278341 May 17 08:26 libicudata28.so.28 > -rw-r--r-- 1 root root 8278341 May 17 08:28 libicudata28.so.28.0 > -rw-r--r-- 1 root root 1476170 May 17 08:29 libicui18n28.so > -rw-r--r-- 1 root root 1476170 May 17 08:29 libicui18n28.so.28 > -rw-r--r-- 1 root root 1476170 May 17 08:30 libicui18n28.so.28.0 > -rw-r--r-- 1 root root 47104 May 17 08:30 libicuio28.so > -rw-r--r-- 1 root root 47104 May 17 08:30 libicuio28.so.28 > -rw-r--r-- 1 root root 47104 May 17 08:30 libicuio28.so.28.0 > -rw-r--r-- 1 root root 196612 May 17 08:30 libicule28.so > -rw-r--r-- 1 root root 196612 May 17 08:30 libicule28.so.28 > -rw-r--r-- 1 root root 196612 May 17 08:30 libicule28.so.28.0 > -rw-r--r-- 1 root root 48041 May 17 08:30 libiculx28.so > -rw-r--r-- 1 root root 48041 May 17 08:30 libiculx28.so.28 > -rw-r--r-- 1 root root 48041 May 17 08:30 libiculx28.so.28.0 > -rw-r--r-- 1 root root 63300 May 17 08:30 libicutoolutil28.so > -rw-r--r-- 1 root root 63300 May 17 08:30 libicutoolutil28.so.28 > -rw-r--r-- 1 root root 63300 May 17 08:30 libicutoolutil28.so.28.0 > -rw-r--r-- 1 root root 1025599 May 17 08:30 libicuuc28.so > -rw-r--r-- 1 root root 1025599 May 17 08:31 libicuuc28.so.28 > -rw-r--r-- 1 root root 1025599 May 17 08:31 libicuuc28.so.28.0 > -rwxr-xr-x 1 root root 637233 May 17 08:31 libjlicapi63.so > > I've tried removing the ones that end in .28 and I don't get the errors, > but then the app doesn't work. Do you think the ones that end in .28 > should be symbolic links to either the ones that end in .so or .28.0? > I'd say that normally you have the real file libicuuc28.so.28.0 (for example) and libicuuc28.so and libicuuc28.so.28 would be symbolic links to that file. I think removing those files and running ldconfig again will cure things. FWIW, you may want to check to see if those files are hard linked....just curious. -- May you live in uninteresting times. -- Chinese proverb -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
