-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tfm: cmake: Toolchain not being passed into psa-arch-tests #34962
Comments
is there a corresponding issue upstream at TF-M ? |
This is psa-arch-tests. An issue can be opened here: https:/ARM-software/psa-arch-tests/issues |
@tejlmand is not the right assignee here, added relevant ones. |
@galak this is an upstream TF-M issue, so you could exclude it from the release bug tally. |
Well, it is an issue, since we integrate the PSA arch tests in Zephyr. So I am also fine with the LOW bug here :) |
@ioannisg will do 👍 |
@ioannisg @oyvindronningstad ARM-software/psa-arch-tests#268 allows the API tests to be run with: $ ./scripts/twister -p mps2_an521_nonsecure -N --inline-logs \
-s samples/tfm_integration/tfm_psa_test/sample.tfm.psa_internal_trusted_storage_test If Tested on Darwin with |
Fixed by #35510 |
Describe the bug
When running unit tests for
psa_arch_tests
with TF-M, cmake falls back to the default C compiler, rather than forwarding the correct ARM cross-compiler, resulting in build failure.The use of the host compiler is caused by this: https:/zephyrproject-rtos/trusted-firmware-m/blob/master/psa-arch-tests/api-tests/CMakeLists.txt#L415-L436
Where the compiler is not passed on, but a C compiler is being looked up here:
https:/zephyrproject-rtos/trusted-firmware-m/blob/51cdecd6f9e6b0aa66da45db22f4b478183d472f/psa-arch-tests/api-tests/tools/scripts/target_cfg/CMakeLists.txt#L29
To Reproduce
This will result in trying to run the system C compiler (
/Library/Developer/CommandLineTools/usr/bin/cc
here, on OS X):Expected behavior
The toolchain should be passed on in the cmake function when running the PSA tests.
Additional context
This fix should happen upstream in TF-M, but the issue is being filed here for tracking purposes until it is resolved either upstream and/or downstram in Zephyr's TF-M module.
The text was updated successfully, but these errors were encountered: