Emacs on a reMarkable

["Sébastien Lerique" <sl@eauchat.org>]

Dear Guix,

I hope this finds you all well!

I'm trying out ways to get emacs running on a reMarkable 2, as there are
now at least two shells that can run aside from the main binary: yaft
<https://github.com/timower/rM2-stuff/tree/master/apps/yaft> and ReTerm
<https://github.com/i-am-shodan/ReTerm/> (which may be ending soon as
yaft is making good progress). There are ongoing conversations with a
Discord community <https://discord.gg/qEnCVcd>, channel called "rm2".

As Rust can't yet be cross-compiled (as far as I know), I set up an ARM
VM with Debian (following
<https://www.willhaley.com/blog/debian-arm-qemu/>), then

  apt install guix
  guix pack -RR -S /emacsbin=bin emacs-no-x

I copy and extract the package in reMarkable. Then, as / and /home are
different partitions on reMarkable, and / is too small, I follow the way
Entware packages are installed (see https://toltec-dev.org/ for
details), so:

  mount -o bind /home/root/gnu /gnu

At this point emacs-no-x runs perfectly when connecting through ssh and
running it there.

But when run from yaft (and from ReTerm), the following error appears,
and emacs (as well as the minimal bash) fails to run:

--8<---------------cut here---------------start------------->8---
/gnu/store/97xwzdsw9p6019dbml5mzf781c7avfkq-bash-minimal-5.1.8/bin/bash: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
--8<---------------cut here---------------end--------------->8---

I can't find libQt5Core* in the tar.gz file, in /gnu/store, and not even
in the /gnu/store on my laptop where I use the guix packaging in
ubuntu/debian to use emacs. Am I maybe not searching properly with the
following?

  find /gnu/store -name "*libQt5*"

I also don't find *libQt5* when I package emacs instead of emacs-no-x. i
tried making the `env` outputs of the ssh shell and the yaft shell match
each other a little more, with no success (I can send them if it makes
sense).

Are there any ideas to figure out what could lead to this bug?

Thanks for everything you are and do!
Sébastien