Shades of the mvebu debate and catering to the lowest common denominator...
Here's another attempt to find a solution.
openwrt:master ← cotequeiroz:wolfssl-cpu-crypto
opened 02:12AM - 08 Aug 22 UTC
libwolfssl-cpu-crypto is a variant of libwolfssl with support for
cryptographic… CPU instructions on x86_64 and aarch64.
On aarch64, wolfSSL does not perform run-time detection, so the library
will crash when the AES functions are called. A preinst script attempts
to check for support by querying /proc/cpuinfo, if installed in a
running system. When building an image, the script will check the
DISTRIB_TARGET value in /etc/openwrt_release, and will abort
installation if target is bcm27xx.
Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
----
This was tested on mediatek, using the regular build system, installing it into a running system, and building an image with the image builder.
Marking the package non-shared had made updates a lot more problematic for everyone. This should be less intrusive to the rest of the ecosystem.
1 Like
Ansuel
August 17, 2022, 12:12pm
43
seems an interesting solution, the fact that this is limited to 2 target is very good... still I'm with the idea that IMHO we should add a way to select the default ssl package for a specific target.
I like this solution, seems a good compromise.
2 Likes