Skip to content

libwolfsslcpu-crypto: conflicts with libwolfssl #20347

Closed
@McGiverGim

Description

@McGiverGim

Maintainer: @cotequeiroz
Environment: IPQ807x, AX3600, snapshot

Description:
The package libwolfsslcpu-crypto is included by default in the list of packages for my device (Xiaomi AX3600). OpenWrt builders are building it without problem, but if fails in other circunstances:

  • While trying to use Attended Sysupgrade. Validating the packages it detects a conflict and fails.
  • While trying to use Firmware Selector. Validating the packages it detects a conflict and fails.
  • If I remove the package from any of the two firmware builders, the firmware is built, but if I try to install it later with opkg it throws an error because the conflict. I can force the installation and all seems to work, but I suppose is not the way to do it.

This is a sample of the error using Firmware Selector:

[libwolfsslcpu-crypto] Checking for Arm v8-A Cryptographic Extension support: ...[offline]... OK
[libwolfsslcpu-crypto] Checking for Arm v8-A Cryptographic Extension support: ...[offline]... OK
Collected errors:
 * check_data_file_clashes: Package libwolfsslcpu-crypto5.5.4.e624513f wants to install file /home/aparcar/asu/worker1/cache/SNAPSHOT/ipq807x/generic/build_dir/target-aarch64_cortex-a53_musl/root-ipq807x/usr/lib/libwolfssl.so.5.5.4.e624513f
	But that file is already provided by package  * libwolfssl5.5.4.e624513f
 * opkg_install_cmd: Cannot install package libwolfsslcpu-crypto.
 * check_data_file_clashes: Package libwolfsslcpu-crypto5.5.4.e624513f wants to install file /home/aparcar/asu/worker1/cache/SNAPSHOT/ipq807x/generic/build_dir/target-aarch64_cortex-a53_musl/root-ipq807x/usr/lib/libwolfssl.so.5.5.4.e624513f
	But that file is already provided by package  * libwolfssl5.5.4.e624513f
 * opkg_install_cmd: Cannot install package libwolfsslcpu-crypto.
make[2]: *** [Makefile:185: package_install] Error 255
make[1]: *** [Makefile:150: _call_manifest] Error 2
make: *** [Makefile:269: manifest] Error 2

Is that an expected behaviour?

EDIT: to give more information, it seems the conflict is exactly with libustream-wolfssl. Both packages are by default in the build. If I remove any of them, the build works, but I don't know if is safe to remove the libustream-wolfssl.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions