Skip to content

Conversation

@Eeems
Copy link
Member

@Eeems Eeems commented Jul 24, 2023

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?

@Eeems Eeems added the packages Add or improve packages of the repository label Jul 24, 2023
@Eeems
Copy link
Member Author

Eeems commented Jul 24, 2023

Well that's odd, when building locally with toltecmk it doesn't fail. Not sure why the exact same image fails here.

@Eeems
Copy link
Member Author

Eeems commented Jul 24, 2023

Okay, next issure. ld-linux-armhf.so.3 is stripped so we don't have debug symbols to work with.

@Eeems
Copy link
Member Author

Eeems commented Dec 26, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

packages Add or improve packages of the repository

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants