A software is being downloaded in a production environment. However, Requires: libsasl2.so.2 () (64bit) is output.

version: CentOS Linux release 7.6.1810 (Core)

The package of LDAP or MYSQL is not necessary, but the following is output.

Installing in CentOS 7 getting failed with the following error.
Error: Package: xxxxxxxxx
Requires: libsasl2.so.2 () (64bit)

When I search on Google, I get past questions etc.

cd/lib64 ln -s libsasl2.so.3.0.0 libsasl2.so.2 yum install mysql-community-server

It is as above, but I don't want to install yum install mysql-community-server etc. .

If there is a package I want to download now, and Requires: libsasl2.so.2 () (64bit) is output,
Will it be solved only by the following? Or is there a way to install Requires: libsasl2.so.2 () (64bit) manually?

cd/lib64 ln -s libsasl2.so.3.0.0 libsasl2.so.2

I researched a lot, and others put on symbolic


usr/lib64/libsasl2.so.2->/usr/lib64/[your sasl version-mine is libsasl2.so.3.0.0]

or rpm is installed, but what I want to install (software not used by general users) is something like MarkLogic-RHEL7-8.0-5.x86_64.rpm

thanks both for answers-I took this one:] # rpm -i MarkLogic-RHEL7-8.0-5.x86_64.rpm-and only had to install yum install glibc.i686-and that did it.MarkLogis started now and console working fine.

I've been thinking for a long time, but if you see this message: Requires: libsasl2.so.2 () (64bit),
Is it possible to solve it by installing Requires: libsasl2.so.2 manually from somewhere?
In that case, where should I download it? . The reason is
Looking up, it looks like it is on the following site, but curl and get this and dropped it to local



rpm -i is scary. . Please tell me how to solve it.

  • Answer # 1

    List the results of the investigation

    libsasl2.so.2 is not in CentOS7.

    As a correspondence, add a symbolic link to libsasl2.so.3.

    ln -s /lib64/libsasl2.so.3.0.0 /lib64/libsasl2.so.2

    If libsasl2.so.3 is not installed in the current environment, install cyrus-sasl-lib.

    This package is available on the installation media and in the Base repository, so use it as you like.

  • Answer # 2


    Because I'm scared to hit rpm -i

    It's hard to tell because it's scary, but if you install rpm, there's a fear that some startup script will run.
    However, if you check the file configuration in advance, you can check whether there is a startup script.

    How about using rpm2cpio to check individual files in rpm?
    I think the following articles will be helpful.
    Extract files from rpm package
    It seems to work if you only get and place files from rpm that also contains libsasl2.so.2 () (64bit).

    However, if libsasl2.so.2 included in rpm is not reliable in the first place, I think that you will build rpm from srpm yourself.

    Imagine that you can only rely on the source if you can't trust the rpm created from srpm.