Define OMR build env for ARM cross-compile #2328
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
When building using OMR_CROSS_CONFIGURE the tools and environment that the OMR tools will be built with must be specified since they cannot be detected by autoconf. Signed-off-by: Younes Manton <[email protected]>
|
Jenkins test sanity all all |
pshipton
approved these changes
Jul 11, 2018
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.
When building using
OMR_CROSS_CONFIGUREthe tools and environment that the OMR tools will be built with must be specified since they cannot be detected by autoconf.This fix is needed once eclipse-omr/omr#2406 goes in but can be merged prior in order to avoid breakage.