Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility issue with Ubuntu 22.04 #47

Closed
jahudka opened this issue Apr 23, 2022 · 5 comments
Closed

Compatibility issue with Ubuntu 22.04 #47

jahudka opened this issue Apr 23, 2022 · 5 comments

Comments

@jahudka
Copy link

jahudka commented Apr 23, 2022

Hi, ReaPack depends on libcrypto.so.1.1, which doesn't seem to exist on Ubuntu 22.04, because the distribution upgraded to libcrypto.so.3 (as part of an upgrade to libssl3).

A working temporary solution is to add the Impish security repository and install libssl1.1 from there; e.g.:

# this URL works on the Raspberry Pi flavour of Ubuntu:
echo 'deb http://ports.ubuntu.com/ubuntu-ports impish-security main' | sudo tee /etc/apt/sources.list.d/impish-security.list
sudo apt-get update
sudo apt-get install libssl1.1

I don't have any idea on the possible system-wide ramifications of doing this, but for now I know of no other way to get ReaPack working on Ubuntu 22.04. Is it at all possible to add support for OpenSSL 3 so that ReaPack can pick at runtime whichever OpenSSL version is available?

@cfillion
Copy link
Owner

cfillion commented May 2, 2022

Working on adding support for OpenSSL 3 without losing compatibility with systems still shipping OpenSSL 1.1. In the meantime, ReaPack can be built from source on Ubuntu 22.04 to be linked against libssl3:

sudo apt install build-essential cmake git php-cli libboost-dev catch2 libcurl4-openssl-dev libxml2-dev libssl-dev libsqlite3-dev zlib1g-dev
git clone --recursive https://github.com/cfillion/reapack.git
cd reapack
CXXFLAGS=-Wno-deprecated-declarations cmake -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build --target install

(The last line also installs the produced binary into ~/.config/REAPER/UserPlugins`)

@acebone
Copy link

acebone commented May 3, 2022

you have a typo in your apt install line: It's not 'build-essentials' but 'build-essential' (without the trailing 's')

Otherwise the build went smoooooth - Reaper now has the appropriate reapack-actions, and all seems to work well. There's no Reapack entry in the "extensions" menu, but that may be a menu/toolbar problem? I don't care, I never use the menu for reapack, I use my custom toolbar, but thought you might like to know. Thanks for the help!

@tubegeek
Copy link

tubegeek commented May 7, 2022

I can confirm that the installation method described works - minus one "s" as noted above. Also with a stock theme, the Extensions menu is indeed present.

Thanks again and again for the development work. Amazing resource.

Question: which of the tools I installed for compiling can I safely uninstall now? Half a gig of development software may be too much to tote around if I'm not going to use it for much else. Thank you.

@cfillion
Copy link
Owner

cfillion commented May 8, 2022

Question: which of the tools I installed for compiling can I safely uninstall now?

They can all be uninstalled once ReaPack is compiled.

(Fixed the typo in the apt line)

cfillion added a commit to cfillion/reapack.com that referenced this issue May 9, 2022
@cfillion
Copy link
Owner

cfillion commented May 9, 2022

Binaries compatible with both OpenSSL 1.1 and 3.0 here: x86_64 & others ("Artifacts" tab). Will do a release in the coming days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants