meta-microblaze: binutils: fixes to Microblaze support patchset #45
Conversation
This file contains 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
The current patchset does not build a working binutils and causes aborts while trying to disassemble code. This newly added patch intends to fix the issue (see patch commit message). Note that it may be preferable to integrate the change in the original patchset.
|
Thank you. We're working on a general update to the branches that should be done next week. Once that goes out, I'll look to integrate this. I will pass it on to our toolchain team for further review. Thanks! |
|
Thanks @mhatle! Awaiting your update then. Feel free to reach out when ready; I will be around to update this pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current patchset does not build a working binutils and causes aborts while trying to disassemble code. This pull request provides a necessary patch to fix the issue. Please refer to the patch commit message for more information.
This change has been testing successfully with upstream OE (
kirkstonebranch).I would recommend updating the original patchset as the issue is likely present in other branches.