Yocto: parsec compilation failed with error: unexpected argument 'mbed-crypto-provider' found

[sahilnxp]

Hi,

I am getting issue in compiling parsec-service with walnascar yocto project

Sstate summary: Wanted 8 Local 1 Mirrors 0 Missed 7 Current 481 (12% match, 98% complete)##########################################################################################                  | ETA:  0:00:00
Initialising tasks: 100% |###########################################################################################################################################################################| Time: 0:00:02
NOTE: Executing Tasks
ERROR: parsec-service-1.4.1-r0 do_compile: Execution of '/home/user/bsp/build/tmp/work/armv8a-poky-linux/parsec-service/1.4.1/temp/run.do_compile.3984232' failed with exit code 1
ERROR: Logfile of failure stored in:/home/user/bsp/build/tmp/work/armv8a-poky-linux/parsec-service/1.4.1/temp/log.do_compile.3984232
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: Using rust targets from /home/user/bsp/build/tmp/work/armv8a-poky-linux/parsec-service/1.4.1/rust-targets/
| NOTE: cargo = /home/user/bsp/build/tmp/work/armv8a-poky-linux/parsec-service/1.4.1/recipe-sysroot-native/usr/bin/cargo
| NOTE: cargo build -v --frozen --target aarch64-poky-linux-gnu --release --manifest-path=/home/user/bsp/build/tmp/work/armv8a-poky-linux/parsec-service/1.4.1/parsec-service-1.4.1//Cargo.toml  --features mbed-crypto-provider,pkcs11-provider,cryptoki/generate-bindings  mbed-crypto-provider pkcs11-provider cryptoki/generate-bindings
| error: unexpected argument 'mbed-crypto-provider' found
|
| Usage: cargo build [OPTIONS]
|
| For more information, try '--help'.
| WARNING: exit code 1 from a shell command.
ERROR: Task (/home/user/bsp/sources/meta-security/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.4.1.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1432 tasks of which 1431 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/user/bsp/sources//meta-security/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.4.1.bb:do_compile
    log: /home/user/bsp/build/tmp/work/armv8a-poky-linux/parsec-service/1.4.1/temp/log.do_compile.3984232
Summary: There was 1 ERROR message, returning a non-zero exit code.

Any idea what I am missing here ?

Regards,
Sahil Malhotra

[anta5010]

@sahilnxp thank you for the report. This issue was introduced by this poky change:
https://git.yoctoproject.org/poky/commit/meta/classes-recipe/cargo.bbclass?id=7a2b9acef2aee730c7bdf641627428c70d3fbbbd

I really don't like the change. It includes PACKAGECONFIG_CONFARGS into cargo command line unconditionally and we don't need that for the parsec-service recipe. I'll try to find a work-around.

[anta5010]

Parsec is not the only recipe broken with the poky change. See the discussion
https://lore.kernel.org/openembedded-core/3e8eedef-b9a9-458e-a3a7-dd86db2f21bc@gmail.com/

[sahilnxp]

Thanks @anta5010 for confirming this issue, Will wait for the workaround for this issue.

[anta5010]

Sorry for the lack of responses.

I posted a fix into meta-parsec more than a month ago:
https://lore.kernel.org/all/20250519084553.2027324-1-Anton.Antonov@arm.com/

But, unfortunately the maintainer of meta-security (which meta-parsec is a a sub-layer of) is retiring and a new maintainer hasn't been found yet:
https://lore.kernel.org/all/20250623202701.12590-1-akuster808@gmail.com/

So, merging the fix in might take longer than usual.

[anta5010]

The fix was merged into the master branch of meta-security and will be included into the next Yocto release (whinlatter):
https://git.yoctoproject.org/meta-security/commit/?id=b1f1c7a304de33916040928ea7182c03580efb28

It will also be merged into walnascar when the new meta-security maintainers finish recreating a working CI setup