From: Gyorgy Sarvari <skandigraun@gmail.com>
To: martin.jansa@gmail.com, raj.khem@gmail.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-initramfs][PATCH] klibc.bbclass: Add spaces around assignment
Date: Fri, 18 Apr 2025 14:25:40 +0200 [thread overview]
Message-ID: <6af6f2ee-a84f-4c17-bb3c-3bd65aa23297@gmail.com> (raw)
In-Reply-To: <CA+chaQewE4WX=DXQv17=aw2etQLj4wxJ_hmtHDY0zaGFgerpBA@mail.gmail.com>
On 4/18/25 13:30, Martin Jansa via lists.openembedded.org wrote:
> On Fri, Apr 18, 2025 at 3:41 AM Khem Raj via lists.openembedded.org
> <raj.khem=gmail.com@lists.openembedded.org> wrote:
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> ---
>> meta-initramfs/classes/klibc.bbclass | 11 ++++++++---
>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta-initramfs/classes/klibc.bbclass b/meta-initramfs/classes/klibc.bbclass
>> index ca50a3d431..935ee10c40 100644
>> --- a/meta-initramfs/classes/klibc.bbclass
>> +++ b/meta-initramfs/classes/klibc.bbclass
>> @@ -9,8 +9,13 @@ CC:append:armv7ve = " ${@' -mfloat-abi=${TUNE_CCARGS_MFLOAT}' if (d.getVar('TUNE
>> CC:append:armv7a = " ${@' -mfloat-abi=${TUNE_CCARGS_MFLOAT}' if (d.getVar('TUNE_CCARGS_MFLOAT') != '') else ''}"
>>
>> # klcc uses own optimizations by default. See klcc(1) man file.
>> -export CFLAGS="${TUNE_CCARGS} ${DEBUG_PREFIX_MAP}"
>> -export CPPFLAGS="${TUNE_CCARGS}"
>> -export LDFLAGS="${TUNE_CCARGS}"
>> +CFLAGS = "${TUNE_CCARGS} ${DEBUG_PREFIX_MAP}"
>> +CFLAGS[export] = "1"
>> +
>> +CPPFLAGS = "${TUNE_CCARGS}"
>> +CPPFLAGS[export] = "1"
>> +
>> +LDFLAGS=" ${TUNE_CCARGS}"
>> +LDFLAGS[export] = "1"
> Why the change in export syntax, is the varflag preferred now?
Meta comment: maybe it should be preferred... It is at least a bit
confusing that bitbake's and shell's "export" look and work very very
similarly, but one of them complains about not having spaces, and the
other complains about having spaces.
next prev parent reply other threads:[~2025-04-18 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 1:41 [meta-initramfs][PATCH] klibc.bbclass: Add spaces around assignment Khem Raj
2025-04-18 11:28 ` [oe] " Gyorgy Sarvari
2025-04-18 11:30 ` Martin Jansa
2025-04-18 12:25 ` Gyorgy Sarvari [this message]
2025-04-18 15:11 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6af6f2ee-a84f-4c17-bb3c-3bd65aa23297@gmail.com \
--to=skandigraun@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.