Standalone version isn't standalone, beside being broken

[necessarily-equal]

Hi,

I've tried to build the software with Nix, send it with scp and run it. I get the following error with the standalone version:

reMarkable: ~/ ./rM2-vnc-server-standalone 
./rM2-vnc-server-standalone: error while loading shared libraries: libcrypto.so.1.0.2: cannot open shared object file: No such file or directory

I have /usr/lib/libcrypto.so.1.1 instead. Settings report "software version 2.6.2.75".

I'm not sure why the binary has any external dependency. I get the impression it's not meant that way

[corwin-of-amber]

Same with 2.7. Probably have to rebuild the libraries in nix-remarkable...

[corwin-of-amber]

Trying to build with nix-remarkable, it now breaks completely as openssl 1.0.2 is marked as obsolete.

e.g.

nix run --arg release true -f . rm2Pkgs.rM-vnc-server
error: Package ‘openssl-1.0.2u’ in /nix/store/631268hv7b3i6mkiv976k29fdjflyd35-source/pkgs/development/libraries/openssl/default.nix:140 is marked as insecure, refusing to evaluate.


Known issues:
 - Support for OpenSSL 1.0.2 ended with 2019.

Trying to build without --arg release true or by cloning this repo in pkgs results in

error: anonymous function at /nix/store/y4ma568zs0pqgxwq7jpcqdsyaixzg3rj-nixpkgs-21.05pre289536.c58b97674b1/nixpkgs/pkgs/os-specific/linux/kernel/manual-config.nix:16:4 called without required argument 'lib', at /nix/store/y4ma568zs0pqgxwq7jpcqdsyaixzg3rj-nixpkgs-21.05pre289536.c58b97674b1/nixpkgs/lib/customisation.nix:69:16

Apologies for my severely limited Nix debugging capabilities.

[pl-semiotics]

Thank you to both of you for these reports.

I believe the issue that @necessarily-equal discovered is the same as #8; the issue is that the development toolchain from reMarkable AS did not match the new system software version. It will be fixed shortly.

The issue that @corwin-of-amber discovered is somewhat more concerning---particularly the fact that the openssl library deprecation notice appeared during the release build. (The issue with the non-release build is unfortunate, but not necessarily unexpected given the number of breaking changes to the cross infrastructure in nixpkgs.) I am not at all sure why the openssl derivation would be being pulled in at all with the released version of the overlay, and even less sure why it would be getting the package that is marked insecure. I will investigate this in more detail as soon as possible.

[necessarily-equal]

Hi, I think I intended to open a new issue about it not being standalone instead of it being broken. But the "broken" got over. I've updated the issue so that it isn't such a duplicate.

I've tried a bit to force a static build, but I must say I couldn't figure something that worked. I'll make a PR with tiny fixes I figured out a bit later. But those won't really help fix it I'm afraid.

[pl-semiotics]

Apologies for the delay in replying here.

Making completely statically linked binaries on a glibc system is quite difficult. Since glibc must be dynamically linked anyway, and since I have had some concerns about memory pressure, I have generally opted to have the -standalone versions mean "this bundles all of the dependencies not present in the system software", since that is what I need the most for my use cases (and I did not bother adding an everything-except-glibc-static version in order to reduce the number of build configurations I must keep track of.)

If you require fully static binaries, it is possible to achieve these as well, but I have not put much effort into doing so recently, since I prefer the "static-except-for-system-libraries" versions for my own use cases.

[neg3ntropy]

Is there a build somewhere with a fix for the libcrypto version?