meta-digi/meta-digi-arm/recipes-bsp/trustfence-cst
Gabriel Valcazar f02d6f9f3c trustfence-cst: use the same toolchain when building internal openssl and cst
An internal build of openssl is compiled as part of the cst build process,
which is later linked statically to the tool. When building the nativesdk
version of cst, openssl's internal "Configure" tool chooses Yocto's nativesdk
compiler for its compilation (x86_64-deysdk-linux-gcc). However, cst's Makefile
uses host tools by default, meaning it will compile its C files with the host's
gcc and link the final binary with the host's ld. This can lead to errors due
to the Yocto nativesdk compiler including symbols in the openssl libraries that
are unknown to the host's linker.

For example, when attempting to build nativesdk-trustfence-cst in Yocto 5.0 on
Ubuntu 2020.04, the following linker error appears multiple times:

undefined reference to `__isoc23_strtol'

Fix this by making sure cst uses the same toolchain as the one used when
building the internal openssl libraries (and ultimately, when the final binary
is linked together). This doesn't affect the native version of cst, which uses
the host's toolchain.

Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
2024-10-28 16:22:16 +01:00
..
trustfence-cst-3.3.2 dey: cosmetic, mark patches as DEY specific 2024-10-22 15:48:00 +02:00
nativesdk-trustfence-cst_3.3.2.bb Update Digi Copyright header 2024-07-15 09:28:58 +02:00
trustfence-cst-3.3.2.inc trustfence-cst: use the same toolchain when building internal openssl and cst 2024-10-28 16:22:16 +01:00
trustfence-cst-native_3.3.2.bb Update Digi Copyright header 2024-07-15 09:28:58 +02:00