Draft
Conversation
Member
Author
|
Well that's odd, when building locally with toltecmk it doesn't fail. Not sure why the exact same image fails here. |
Member
Author
|
Okay, next issure. ld-linux-armhf.so.3 is stripped so we don't have debug symbols to work with. |
Member
Author
|
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 Is it worth it? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-valgrindorremarkable-valgrindand mark it as conflicting with valgrind. Thoughts?