Ask Your Question
1

F21: libacl package has no "/lib/libacl.so"?

asked 2015-01-13 19:40:28 -0500

RL gravatar image

Hi,

On my i686 PC I have F21 with acl.i686 and libacl.i686 packages installed. The libacl package gives me following libraries:

/usr/lib/libacl.so.1 -> libacl.so.1.1.0 /usr/lib/libacl.so.1.1.0

I have software that needs java (openjdk), but it complains about following:

WARNING - com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor cannot be used on this system. Got the following error : "java.lang.UnsatisfiedLinkError : no acl in java.library.path"

WARNING - You should check that the 'acl' package is properly deployed on your computer. In most cases, there should be a 'libacl.so' file or symbolic link somewhere on your filesystem. If it is not the case, you should check for a 'libacl.<some number="" version="">.so' file and create a symbolic link named 'libacl.so' on it. If no such file can be found, just install the 'acl' package using your standard package manager.</some>

If I manually create a link "/lib/libacl.so -> /lib/libacl.so.1", then everything works fine.

Shouldn't that link be created automatically when installing the libacl package?

Regards, RL

edit retag flag offensive close merge delete

Comments

Yes, I believe you are correct - it should create that link. You should consider raising a bug against that package, check first that one does not already exist.

cobra gravatar imagecobra ( 2015-01-14 05:55:38 -0500 )edit

OK, I have done just that in bugzilla.

RL gravatar imageRL ( 2015-01-14 09:40:53 -0500 )edit

It turns out that the libacl-devel package will put the libacl.so in place. There seems to be a logic why that is so, but I don't get it. Anyhow, after installing libacl-devel, libacl.so is there :).

RL gravatar imageRL ( 2015-01-15 21:44:16 -0500 )edit

What about if you put the jre package in place rather than the development jdk? Does that create the link, because if you need that link to run some packages and it's not created then there is a bug. It looks like your problem here could have been caused by trying to set up with the developers kit, so you can rule that out.

cobra gravatar imagecobra ( 2015-01-16 03:25:47 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2015-01-16 06:07:54 -0500

tomspur gravatar image

As you already mentioned in the comments above, the libacl-devel package contains the libacl.so symlink and this is generally the case for shared libraries.

The unversioned shared library is always in the devel package. For more explaination see the Packaging Guidelines.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2015-01-13 19:40:28 -0500

Seen: 587 times

Last updated: Jan 16 '15