13

I downloaded freeverb.tar.gz which contains a plugin library (freeverb.so) for Audacity.

I extracted the .tar.gz file to my downloads folder but I don't know what to do next. There is no Readme file or any other info contained in the .tar.gz file, just freeverb.so

Can you advise me how to get the freeverb.so installed into the correct folder for Audacity to pick it up?

thepurpleowl
  • 101
DaveyT
  • 171

3 Answers3

8

According to ubuntu manual:

ldconfig creates, updates, and removes the necessary links and cache (for use by the run-time linker, ld.so) to the most recent shared libraries found in the directories specified on the command line, in the file /etc/ld.so.conf, and in the trusted directories (/usr/lib and /lib).

So, assuming that freeverb.so is located in /home/yourUser/Download directory (folder), create folder in your home:

mkdir /home/yourUser/myLibrary

and copy freeVerb.so library:

cp /home/yourUser/Download/freeverb.so /home/yourUser/myLibrary

create a simple file freeverb.conf like this:

echo "/home/yourUser/myLibrary" > freeverb.conf

Add you configuration file freeverb.conf in /etc/ld.so.conf.d directory (in this directory you can find files as example)

sudo cp freeverb.conf /etc/ld.so.conf.d

Run ldconfig in order to configure dynamic linker run-time bindings.

sudo ldconfig

If /etc/ld.so.conf.d doesn't exists, you can add your path at the end of /etc/ld.so.conf file.

At the end, if all went well, you can remove unnecessary file:

rm freeverb.conf
rm /home/yourUser/Download/freeverb.so
Neuron
  • 107
  • 4
Lety
  • 6,089
  • 2
  • 32
  • 38
0

The simple approach is to put the file in /usr/local/lib, chown the file to root:root, and chmod it to 755.

However, managing system files manually is not something I would personally recommend, so if possible I would search for a prebuilt .deb file for your particular version of Ubuntu.

Score_Under
  • 354
0

You can install the package containing the library in a clean system (such as reference docker container with the same system) and then copy the missing shared library (as reported during failed run attempts) from the installed location (such as /lib/x86_64-linux-gnu/) to exactly the same location in the target system or container.

Be warned that multiple additional packages may need to be installed to extract all the necessary dependencies (a common problem with so-called "distroless" containers). It is therefore best to list all dependencies using ldd to avoid an iterative process.

mirekphd
  • 133