toltec
toltec copied to clipboard
Add valgrind
Entware already contains valgrind, but it's not really useful for things built targeting the reMarkable instead of generic entware. It also appears to be missing some tools.
This does mean that we have a name conflict with the packages. I'm tempted to rename it to toltec-valgrind
or remarkable-valgrind
and mark it as conflicting with valgrind. Thoughts?
Well that's odd, when building locally with toltecmk it doesn't fail. Not sure why the exact same image fails here.
Okay, next issure. ld-linux-armhf.so.3 is stripped so we don't have debug symbols to work with.
It looks like the toolchain contains unstripped versions of the libraries in the arm sysroot. I'm not really sure if it's worth trying to provide them in a package somehow? It would be possible to automate installing the toolchain, and then grabbing the files from the sysroot and stuffing them into a package that bind mounts them into a .debug
folder in /lib
and /usr/lib
or something, whatever valgrind would need to work.
Is it worth it?