mautrix-signal: fix build with goolm, enable checks & version test

[christoph-heiss]

On current master, building mautrix-signal is broken when using witGoolm = true, as it needs to explicitly link to libstdc++ (which is transitivly required).

Further, enable checks on the package, which only need a small workaround for properly finding libstdc++ in the check phase -- hopefully that is acceptable, but maybe there is a better solution to this.

Finally, add a basic version test for the resulting binary with testers.testVersion.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[niklaskorz]

Seems to run fine so far on my own server. Interestingly much better than the last time I testdrove goolm!

[christoph-heiss]

Seems to run fine so far on my own server. Interestingly much better than the last time I testdrove goolm!

Thanks for reviewing & testing!

[niklaskorz]

If this runs sufficiently well, we could consider switching the default to withGoolm ? true in the future.
As the current libolm default results in this package being marked as insecure, it already requires further user configuration to use.

[christoph-heiss]

If this runs sufficiently well, we could consider switching the default to withGoolm ? true in the future. As the current libolm default results in this package being marked as insecure, it already requires further user configuration to use.

Yeah, sounds like a good idea, since - as you say - already requires some form of intervention anyway.