summaryrefslogtreecommitdiffstats
path: root/scripts/contrib/patchreview.py
diff options
context:
space:
mode:
authorTom Hochstein <tom.hochstein@oss.nxp.com>2024-07-25 06:59:32 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2024-07-26 12:28:42 +0100
commitac09753064da6b96199af5d1feedd371b24f1a3a (patch)
treea32c75949dd968648ed2132278c8d66ceacb17d9 /scripts/contrib/patchreview.py
parentedc44fcf135d13e6c514c329ad4d0538ef8faf77 (diff)
downloadpoky-ac09753064da6b96199af5d1feedd371b24f1a3a.tar.gz
time64.inc: Simplify GLIBC_64BIT_TIME_FLAGS usage
The implementation uses the append operator to include GLIBC_64BIT_TIME_FLAGS in TARGET_CC_ARCH, but it places the space in the GLIBC_64BIT_TIME_FLAGS assignment in order to avoid a 'spurious space' when the value is empty. 68b50d3 time64: Remove leading whitespace from GLIBC_64BIT_TIME_FLAGS The problem with this is it requires anyone wishing to assign a value to GLIBC_64BIT_TIME_FLAGS to add the leading space, otherwise this is the error: cc1: error: '-Werror=format-security-D_TIME_BITS=64': no option '-Wformat-security-D_TIME_BITS=64' Add a new constant variable to capture the value needed for the 32-bit special case, including the space. (From OE-Core rev: e8177827f92e71c80c5b63453d8bbd1defbe1fbc) Signed-off-by: Tom Hochstein <tom.hochstein@oss.nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/contrib/patchreview.py')
0 files changed, 0 insertions, 0 deletions