u-boot-k3: set EXTRA_OEMAKE for openssl 4.x

[Trevor Gamblin (threexc)]

Description

I missed this with the previous fix for the K1 boards. Below is the commit description.

OpenSSL was upgraded to 4.0.1 in oe-core commit 20bf704e58. This removes engine support and the ENGINE API, starting in openssl commit 5ef339776d, where if OPENSSL_ENGINE_STUBS is defined the relevant engine macros are set to 0. As with commit 666c8f7, this change breaks u-boot-k3 on the do_compile step, so modify EXTRA_OEMAKE to set HOSTCFLAGS_rsa-sign.o (found in U-Boot's tools/Makefile) to generate the stubs. The '-Wno-deprecated-declarations' flag seems to be mainly for OS X, but preserve it anyway to minimize the scope of our change.

Checklist

• I have read and understood the Contributing Changes to a Component and Recipe Style Guide sections in the Yocto Project documentation
• I have tested this change (provide brief details below)
• Documentation has been added/updated where necessary in the README and docs/
• If the change is to a BSP in
  DEPRECATED.md,
  then it is maintenance-only, i.e. it does not add support for a
  previously-removed BSP (or significant features to one slated for removal)
• (For new/modified BSPs) I have added relevant information in the README table
• (For new/modified BSPs) The bitbake-setup templates in bitbake-registry/
  have been updated, if necessary
• (For new/modified BSPs) A kas file has been provided in kas/
• I have added my Signed-off-by and any other tags to each commit

How has this been tested?

Provide a brief summary here (e.g. build only, build + boot test, something more
specific). Boot logs, images, or other artifacts are especially helpful.

Local test of a u-boot-k3 build. Also running against my CI: https://forgejo.baylibre.com/tgamblin/boardgarden/actions/runs/388/jobs/0/attempt/1

[Khem Raj (kraj)]

FWIW, I think this patch is not right to fix the problem. There is upstream patch series - https://www.mail-archive.com/u-boot@lists.denx.de/msg564619.html which is modeled around similar patch for kernel. Whenever that lands in u-boot, we should pick that up instead.

[Trevor Gamblin (threexc)]

FWIW, I think this patch is not right to fix the problem. There is upstream patch series - https://www.mail-archive.com/u-boot@lists.denx.de/msg564619.html which is modeled around similar patch for kernel. Whenever that lands in u-boot, we should pick that up instead.

I'll keep an eye on this and submit a correct fix as soon as possible.

[Khem Raj (kraj)]

FWIW, I think this patch is not right to fix the problem. There is upstream patch series - https://www.mail-archive.com/u-boot@lists.denx.de/msg564619.html which is modeled around similar patch for kernel. Whenever that lands in u-boot, we should pick that up instead.

I'll keep an eye on this and submit a correct fix as soon as possible.

see - YoeDistro/meta-variscite-bsp@d8e2a66

Perhaps this will help ?

[Trevor Gamblin (threexc)]

FWIW, I think this patch is not right to fix the problem. There is upstream patch series - https://www.mail-archive.com/u-boot@lists.denx.de/msg564619.html which is modeled around similar patch for kernel. Whenever that lands in u-boot, we should pick that up instead.

I'll keep an eye on this and submit a correct fix as soon as possible.

see - YoeDistro/meta-variscite-bsp@d8e2a66

Perhaps this will help ?

Sure, I'll submit a corresponding PR for meta-riscv.