add LDFLAGS in OUTCMD to fix YOCTO QA issues

[jamin-aspeed]

Users can set "LDFLAGS" of Yocto build environment in LFLAGS_END variable to fix "ldflags" QA error. However, the source files use "LFLAGS_END" variable to show the compiler flag information.

Compiler version : GCC13.2.0
Compiler flags   : -O2 -DMULTITHREAD=2 -DUSE_FORK -pthread  -lrt

LDFLAGS of Yocto build environment includes the build path and it causes "buildpath" QA warning/error. To fix all QA errors/warnings, adds LDFLAGS in the OUTCMD.

[joseph-yiu]

Hi @jamin-aspeed ,
We are looking into preparing a maintenance release. Could you let us know if this pull request is still valid? (Just in case anything has changed in YOCTO that might affect this).
Thanks and regards,
Joseph

[jamin-aspeed]

Hi @joseph-yiu

Thanks for checking.

I re-tested this with the latest CoreMark version using commit:
1f483d5

Without this pull request, I still encounter build failures and QA errors as shown below:

ERROR: coremark-git-r0 do_package_qa: QA Issue: File /usr/bin/coremark_4thread in package coremark doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags]
ERROR: coremark-git-r0 do_package_qa: QA Issue: File /usr/bin/coremark_2thread in package coremark doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags]
ERROR: coremark-git-r0 do_package_qa: QA Issue: File /usr/bin/coremark_1thread in package coremark doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags]
ERROR: coremark-git-r0 do_package_qa: Fatal QA errors were found, failing task.

The recipe I used for building CoreMark is:
https://github.com/AspeedTech-BMC/openbmc/blob/aspeed-master/meta-aspeed-sdk/recipes-benchmark/coremark/coremark_git.bb

So from my testing, this pull request is still required for the current Yocto/OpenBMC environment.

Thanks and regards,
Jamin

[joseph-yiu]

Thanks for your quick response. We will add this to the list.
Now merged into development branch (dev_2026q3).
regards,
Joseph