Does building instruction work on RPi4 64 bit OS?

[dasrocky]

I am trying to build latest stable qbittorrent for raspberry pi 4. I had issues with qbittorrent(v4.2 i think) webui stops working after a while. I tried to fix it but didnt work. So i tried going with v4.4.x but going through the documentation for building RPi4, got some errors while building libtorrent such as "configure: error: --with-boost-libdir expected directory name" and "configure: error: Could not find a version of the Boost::System library!". So i created the directory and installed "sudo apt-get install libboost-all-dev" respectively. Well that didn't work either.

Question: Does this instruction on building qbittorrent works on rpi4 64bit armv8? if yes, then what am doing wrong and getting such errors

Specs:
SBC: RPi4
OS: Dietpi v8.4 64bit - Debian bullseye - trimmed version of raspbian server os
RAM: 4GB

[Kolcha]

manual you mentioned seems to be not suitable for arm64 (aarch64) because it mentions arm-linux-gnueabihf which definitely means 32-bit ARM, for 64-bit it should look different. as solution, I suggest just to drop this --with-boost-libdir part, system library should be detected correctly, option is required when you are building with custom boost. another option - consider to use cmake instead of autotools, it doesn't have such confusing options and definitely searches system libraries by default.

also I would like to suggest just to add my custom repository (it has builds for Raspbian for both 32 and 64 bit ARM) and just install qbittorrent / qbittorrent-nox package (libtorrent-rasterbar package will also be installed/updated)
https://software.opensuse.org//download.html?project=home%3Anikoneko%3Atest&package=qbittorrent
instead of building from source. build it from source only if something is not suitable for you (or just binaries don't work).

[dasrocky]

I suggest just to drop this --with-boost-libdir part, system library should be detected correctly

It worked. I tried installing as u suggested. If u don't mind telling me, what does that command do with and without --with-boost-libdir and custom boost.

I am not sure should I make an issue regarding this or not. After compiling it, works fine manually:

• export LD_LIBRARY_PATH=/usr/local/lib:${LD_LIBRARY_PATH}
  which gives no error symbol lookup error: qbittorrent-nox: undefined symbol: _ZN10libtorrent7session5startENS_5flags13bitfield_flagIhNS_17session_flags_tagEvEEONS_14session_paramsEPN5boost4asio10io_contextE
• qbittorrent-nox
  

But the problem arises when I run using systemd service:

• 
  I guess I know the issue, I just have to do this "export LD_LIBRARY_PATH=/usr/local/lib:${LD_LIBRARY_PATH}", i tried adding it .profile but sadly no luck. I even checked in Dietpi scripts to install Debian bullseye qbittorrent package, didn't find any solution for it either. I am sure, that I am missing a simple step, please note i am still new in this.

[Kolcha]

this option just forces configure script to use specific path when looking for boost (in this particular case), no any other places are considered. without this option search is performed in default places (i.e. in /usr/lib and /usr/lib/<arch-specific>) where all libraries are installed from packages are located.
"custom boost" means Boost library compiled from sources rather than installed from package (like you did by running sudo apt-get install libboost-all-dev). in such case (Boost was compiled manually) configure script has no chance to find it (actually it is possible in some cases, when it is installed to /usr/local for example, but not always), and then this option is definitely required. it is also can be useful (or even necessary) in case of cross-compilation.

about missing symbols, few cases are possible:

• the first one looks like you have 2 different libtorrent libraries in you system: one was installed from package (when you installed qbittorrent from repository) and located somewhere in /usr/lib, another one (required, which was compiled from source) is located in /usr/local/lib.
• another one (if one library exists in the system) is just a dynamic linker configuration - dynamic linker just doesn't look into /usr/local/lib to resolve all required symbols on executable launch. I observed such behavior in few Debian-based systems. in such case everything you need is just to add /usr/local/lib to search paths. google for "ld.so.conf" or "ldconfig" or look here for example (other path is added, but it doesn't matter). usually after changing this config you should run ldconfig

[dasrocky]

Thanks for info and taking time in typing that, learning as I go.

you need is just to add /usr/local/lib

Did these steps from compilation docs for rpi but didn't know how to do it in service file. Lucky, after some time found a solution

Actually I found solution while ago and then took a break😅. Solution from here askubuntu, by just adding Environment=LD_LIBRARY_PATH=/usr/local/lib:${LD_LIBRARY_PATH} in service file.

[Kolcha]

Did these steps from compilation docs for rpi but didn't know how to do it in service file. Lucky, after some time found a solution

I wrote this regardless of mentioned manual... Just from my own experience. even didn't know that this manual says the same.
this change has a system-wide effect, not only for specific executable or service file. it affects everything. but depending on distro, the way to achieve this may slightly vary (but in general it is the same - just to add /usr/local/lib path somewhere), and in many cases it has no effect until some command (like ldconfig) is run or even system reboot.

the thing you did affects only a specific service file, this is fine and enough, and completely safe.

[dasrocky]

sorry for late reply.

just to add /usr/local/lib path somewhere and ldconfig

Did that from the manual. But didn't work for service to start the app, weirdly. Anyway now it is running by adding it in service file

the thing you did affects only a specific service file, this is fine and enough, and completely safe

Yeah. I don't need it system-wide for now, just only for qbittorrent to run, so I just added it to its own service file.

Thank you again for information and ur time.