Use a docker image for cross compilation #1
Merged
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
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.
Didn't opt for
cross-rssince they didn't seem to haveriscv32support, instead just used a pre-existing Docker cross compilation image from dockcrossOne thing, the toolchain in this docker image was complaining about
cc1: error: requested ABI requires '-march' to subsume the 'D' extensionwhen using-march=rv32iso march is set torv32idinstead.dseems to enable support for double precision in floating point numbers (if i read this correctly) which I think is irrelevant currently so shouldn't cause any issuesAlso the whole thing is now run from the repository root rather than having to chdir into
src/