Fix native libdir path for multilib #239
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
|
Good question. As you'll see from the build table in the README we follow the Yocto support regime and currently aim to support the five releases there. So I think if this CI builds and tests successfully and nobody raises any issues then we'd look at PRs into those branches? |
niraami
force-pushed
the
fix-multilib-build
branch
from
d815833
to
1c52c9d
Compare
This was referenced Oct 18, 2024
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.
Closes #238
When building for an image with multilib (for 32 bit x86), the
${libdir}variable gets changed from/usr/libto/usr/lib64- butmono-nativestill outputs the libraries into/usr/lib.This is one approach that fixes that issue.
Note: this also should be backported as far back as Kirkstone, maybe further - I dunno what your workflow for that is.