libbz2

[jico448]

I'm trying to run the fah client after updating to the 5.5, but this keeps happening,

'jico448@MainPCEth:~/fah-client_8.5.5-64bit-release$ sudo ./fah-client
[sudo] password for jico448:
./fah-client: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory'

I checked, and I have bzip2-libs installed, 'jico448@MainPCEth:~/fah-client_8.5.5-64bit-release$ sudo dnf install bzip2-libs
Updating and loading repositories:
Repositories loaded.
Package "bzip2-libs-1.0.8-21.fc43.x86_64" is already installed.
Package "bzip2-libs-1.0.8-21.fc43.i686" is already installed.

Nothing to do.'

I'm using fedora linux.

[muziqaz]

Why are you running the client in sudo?

[calxalot]

You might want to build the client yourself:

https://github.com/FoldingAtHome/fah-cl ... ING-RPM.md

[jico448]

Why are you running the client in sudo?

No reason. I'll stop...

[muziqaz]

Why are you running the client in sudo?

No reason. I'll stop...

so after you built the client, cd to fah-client-bastet directory and install it with sudo dnf install ./fah-client-something-something.rpm. After the installation, go to your browser and punch in: v8-5.foldingathome.org, and go from there.
After installation client runs automatically, btw

[jico448]

You might want to build the client yourself:

https://github.com/FoldingAtHome/fah-cl ... ING-RPM.md

I'm trying to build the package, but I'm running into an issue with openssl,

'src/cbang/openssl/KeyPair.cpp:55:10: fatal error: openssl/engine.h: No such file or directory
55 | #include <openssl/engine.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
scons: *** [build/cbang/openssl/KeyPair.o] Error 1
scons: building terminated because of errors.'

I checked and opensl is installed,

'jico448@MainPCEth:~$ sudo dnf install openssl-devel
[sudo] password for jico448:
Updating and loading repositories:
Repositories loaded.
Package "openssl-devel-1:3.5.4-1.fc43.x86_64" is already installed.

Nothing to do.
jico448@MainPCEth:~$ '

I'm trying to figure out why cbang can't find or use openssl on my machine. Any hints?

[muziqaz]

Which fedora version? I managed to build multiple clients for fedora 43, almalinux, fedora 41

[jico448]

Which fedora version? I managed to build multiple clients for fedora 43, almalinux, fedora 41

I'm on fedora 43. I'm looking at the cbang git to try and find solutions, but I'm not seeing anything. I think I'm gonna make an issue post these to try and get to the bottom of this. I've been looking at the build config and it looks like openssl should be included, but I can't figure out why it errors out when it comes to openssl.

[muziqaz]

Which fedora version? I managed to build multiple clients for fedora 43, almalinux, fedora 41

I'm on fedora 43. I'm looking at the cbang git to try and find solutions, but I'm not seeing anything. I think I'm gonna make an issue post these to try and get to the bottom of this. I've been looking at the build config and it looks like openssl should be included, but I can't figure out why it errors out when it comes to openssl.

One sec, I'll try building on my fedora 43. Had no issues before. Are you sure you have all the dependencies from the guide list?

hm, I actually already built 8.5.5 :/ once sec, I'll try again

Did you install openssl-devel-engine?

[jico448]

Which fedora version? I managed to build multiple clients for fedora 43, almalinux, fedora 41

I'm on fedora 43. I'm looking at the cbang git to try and find solutions, but I'm not seeing anything. I think I'm gonna make an issue post these to try and get to the bottom of this. I've been looking at the build config and it looks like openssl should be included, but I can't figure out why it errors out when it comes to openssl.

One sec, I'll try building on my fedora 43. Had no issues before. Are you sure you have all the dependencies from the guide list?

hm, I actually already built 8.5.5 :/ once sec, I'll try again

Did you install openssl-devel-engine?

I did not.

'sudo dnf install openssl-devel-engine
Updating and loading repositories:
Repositories loaded.
Package Arch Version Repository Size
Installing:
openssl-devel-engine x86_64 1:3.5.4-1.fc43 updates 52.8 KiB

Transaction Summary:
Installing: 1 package

Total size of inbound packages is 44 KiB. Need to download 44 KiB.
After this operation, 53 KiB extra will be used (install 53 KiB, remove 0 B).
Is this ok [y/N]: Y
[1/1] openssl-devel-engine-1:3.5.4-1.fc43.x86_64 100% | 68.6 KiB/s | 43.8 KiB | 00m01s
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[1/1] Total 100% | 30.5 KiB/s | 43.8 KiB | 00m01s
Running transaction
[1/3] Verify package files 100% | 500.0 B/s | 1.0 B | 00m00s
[2/3] Prepare transaction 100% | 3.0 B/s | 1.0 B | 00m00s
[3/3] Installing openssl-devel-engine-1:3.5.4-1.fc43.x86_64 100% | 140.0 KiB/s | 68.2 KiB | 00m00s
Complete!'

After installing, the build worked!

'ls fah-client-bastet/
build CHANGELOG.md config.log fah_client-8.5.5-1.x86_64.rpm install package.json README.md scripts TESTING.md
BUILDING-RPM.md CODE_TAG fah-client images LICENSE package.txt SConstruct src'

[muziqaz]

Awesome!
The guide has an extra line under the required dependencies which mentions modern fedora requirement of devel-engine.

[AZBrandon]

I ran into the same problem when trying to run the 8.5 client; I don't have this problem with the 8.4 client. I have Bazzite, so because of the whole "immutable operating system" thing, I can't install or build packages myself, or haven't figured out how to circumvent the Bazzite protection schemes to do so. I'm not sure why this suddenly became a problem in 8.5.5 but 8.4.9 works; though obviously it was some kind of specific change between the versions.

[muziqaz]

I ran into the same problem when trying to run the 8.5 client; I don't have this problem with the 8.4 client. I have Bazzite, so because of the whole "immutable operating system" thing, I can't install or build packages myself, or haven't figured out how to circumvent the Bazzite protection schemes to do so. I'm not sure why this suddenly became a problem in 8.5.5 but 8.4.9 works; though obviously it was some kind of specific change between the versions.

You missed the line of instructions, too? That's not an issue on the client side.

[AZBrandon]

I ran into the same problem when trying to run the 8.5 client; I don't have this problem with the 8.4 client. I have Bazzite, so because of the whole "immutable operating system" thing, I can't install or build packages myself, or haven't figured out how to circumvent the Bazzite protection schemes to do so. I'm not sure why this suddenly became a problem in 8.5.5 but 8.4.9 works; though obviously it was some kind of specific change between the versions.

You missed the line of instructions, too? That's not an issue on the client side.

The instructions are for 8.4: https://foldingathome.org/guides/v8-4-client-guide/

The last line is "PRs are much more likely to be accepted if they are simple and the code is clean and well tested."

I'm not sure what that has to do with the libbz2 problem, but thanks for the tip.

[muziqaz]

I ran into the same problem when trying to run the 8.5 client; I don't have this problem with the 8.4 client. I have Bazzite, so because of the whole "immutable operating system" thing, I can't install or build packages myself, or haven't figured out how to circumvent the Bazzite protection schemes to do so. I'm not sure why this suddenly became a problem in 8.5.5 but 8.4.9 works; though obviously it was some kind of specific change between the versions.

You missed the line of instructions, too? That's not an issue on the client side.

The instructions are for 8.4: https://foldingathome.org/guides/v8-4-client-guide/

The last line is "PRs are much more likely to be accepted if they are simple and the code is clean and well tested."

I'm not sure what that has to do with the libbz2 problem, but thanks for the tip.

Look where you are posting your comments. The topic of the thread is libbz2, and the reason for the thread was that user misread the guide (which is not a massive issue, we all do that from time to time). You come in with something completely different. Your issue is neither libbz2, nor misreading the client build guide related