Installing 2 SDKs of the same version but different arch results in broken compilation
Description
Installing 2 SDKs let's say from 5.99.2:
armv7thf
aarch64
Results in broken compilation options. Likely the SDK installed last overwrites a common file.
This operation mode is actually supported in yocto as each ARCH has a separate env script.
In this case we seem to overwrite a setting that is sourced by both env scripts.
Examples an log output follow.
Environment
None
100% Done
Activity
Walt Miner
April 21, 2020 at 3:21 PM
@Jan-Simon Moeller your thoughts? Can we close this?
Stephane Desneux
April 21, 2020 at 1:32 AM
This is not a simple submit: porting the change to inner class populate_sdk_base.bbclass seems necessary, as well as tests etc. So you can consider that issue as fixed in AGL but not in upstream project. Feel free to reassign to someone who wants to follow this issue on upstream side.
Walt Miner
April 20, 2020 at 10:18 PM
@ronan Le Martret You "Stopped Work" on this ticket and reassigned to me. What needs to be done to complete the ticket? Per @Tom Rini you just need to submit this upstream, so what is the hold up?
Tom Rini
April 16, 2020 at 12:39 PM
For the record, it looks like the "adapt and submit upstream" part hasn't happened at this time.
Major
Installing 2 SDKs let's say from 5.99.2:
armv7thf
aarch64
Results in broken compilation options. Likely the SDK installed last overwrites a common file.
This operation mode is actually supported in yocto as each ARCH has a separate env script.
In this case we seem to overwrite a setting that is sourced by both env scripts.
Examples an log output follow.