recipes-security: optee-imx: optee-*: Upgrade BSP to LF6.6.36_2.1.0

[hiagofranco]

Upgrade optee-client, optee-os and optee-test to new NXP BSP LF6.6.36_2.1.0.

Related-to: #1953

[hiagofranco]

Hi @otavio, on optee-os, I am seeing the following error:

ERROR: optee-os-4.2.0.imx-r0 do_package_qa: QA Issue: File /usr/include/optee/export-user_ta_arm64/lib/libdl.a in package optee-os-staticdev contains reference to TMPDIR [buildpaths]
ERROR: optee-os-4.2.0.imx-r0 do_package_qa: QA Issue: File /usr/include/optee/export-user_ta_arm64/lib/libutee.a in package optee-os-staticdev contains reference to TMPDIR [buildpaths]
ERROR: optee-os-4.2.0.imx-r0 do_package_qa: QA Issue: File /usr/include/optee/export-user_ta_arm64/lib/libmbedtls.a in package optee-os-staticdev contains reference to TMPDIR [buildpaths]
ERROR: optee-os-4.2.0.imx-r0 do_package_qa: QA Issue: File /usr/include/optee/export-user_ta_arm64/lib/libutils.a in package optee-os-staticdev contains reference to TMPDIR [buildpaths]
ERROR: optee-os-4.2.0.imx-r0 do_package_qa: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in: /var/home/frh/freescale/build/tmp/work/imx8qxp_mek-fslc-linux/optee-os/4.2.0.imx/temp/log.do_package_qa.832325

I could not find the root cause of this error in the optee-os source code itself, so I would like to demote this error to a warning:

ERROR_QA:remove:layer-my-layer = "buildpaths"
WARN_QA:append:layer-my-layer = " buildpaths"

but I do not know if this is possible only for optee-os, I think my proposal would do it for the whole freescale layer. What do you suggest here? Should we look more into the code and patch it?

[otavio]

Please take a look at #1983. I prefer to take this recipe by recipe so we can later fix it more properly. I will merge this as this fix is unrelated, and specifically for this recipe, we already have an ongoing pull request.

[github-actions]

Successfully created backport PR #1985 for scarthgap.

[hiagofranco]

Please take a look at #1983. I prefer to take this recipe by recipe so we can later fix it more properly. I will merge this as this fix is unrelated, and specifically for this recipe, we already have an ongoing pull request.

Nice, thank you!