So, the links in /etc/alternatives are pretty messed up in the puritine container. To fix them to the point where LO starts, use the following commands.
This will rebuild the dynamic linker cache inside the container to include the Mesa GL libraries. LO will get past the startup problems (I then get messages associated with incompletely insdtalled dependency packages like libgdk-pixbuf2.0-0 and Java framework errors).
So, the links in /etc/alternatives are pretty messed up in the puritine container. To fix them to the point where LO starts, use the following commands.
$ sudo ln -sf /home/phablet/ .cache/ libertine- container/ smw/rootfs/ usr/lib/ arm-linux- gnueabihf/ mesa/ld. so.conf ../libertine- container/ puritine/ rootfs/ etc/alternative s/arm-linux- gnueabihf_ gl_conf libertine- container/ puritine/ rootfs ldconfig.real -f /usr/lib/ arm-linux- gnueabihf/ mesa/ld. so.conf
$ sudo proot -S ~/.cache/
This will rebuild the dynamic linker cache inside the container to include the Mesa GL libraries. LO will get past the startup problems (I then get messages associated with incompletely insdtalled dependency packages like libgdk-pixbuf2.0-0 and Java framework errors).