public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/3] m4: upgrade to 1.4.21
Date: Wed, 11 Mar 2026 13:17:26 +0800	[thread overview]
Message-ID: <98cccb05-390e-4362-899c-8eace203e970@windriver.com> (raw)
In-Reply-To: <CA+chaQcR9wFdqBCq0GP580-CcfakqM06gadzb=d6m0EseC75qA@mail.gmail.com>

Hi Martin,

On 3/8/26 20:14, Martin Jansa wrote:
> On Sat, Mar 7, 2026 at 4:00 PM Robert Yang <liezhi.yang@windriver.com> wrote:
>>
>> Hi Martin,
> 
> Hi Robert,
> 
> 
>> On 3/6/26 02:03, Martin Jansa via lists.openembedded.org wrote:
>>> From: Martin Jansa <martin.jansa@gmail.com>
>>>
>>> https://lists.gnu.org/archive/html/m4-announce/2026-02/msg00000.html
>>> This release is being made mainly to cater to recent glibc changes in
>>> light of the C23 language standard.  However, it also includes fixes
>>> for some corner-case bugs in eval and when using the defn macro on
>>> builtins.
>>>
>>> Fixes m4-native builds on hosts with glibc-2.43 like:
>>> ./stdlib.h:827:20: error: expected identifier or '(' before '_Generic'
>>> ./string.h:777:20: error: expected identifier or '(' before '_Generic'
>>>
>>> Remove 0001-gettext-h-Avoid-gcc-Wformat-security-warnings-with-d.patch
>>> which is included in gnulib revision used by m4 since:
>>> https://gitweb.git.savannah.gnu.org/gitweb/?p=m4.git;a=commit;h=beee8d26382460010338c37f9dd9f823aa9f4ee8
>>>
>>> LIC_FILES_CHKSUM was updated for barem4.m4 and testbarem4.m4 from:
>>> https://gitweb.git.savannah.gnu.org/gitweb/?p=m4.git;a=blobdiff;f=examples/COPYING;h=e623b2b9394cbd1784a4964bbac105050296f33b;hp=7e73a1219b542fa035facc47cdb3dd81132e6373;hb=900a90f624cee4a8c1c02c4d6a61ef1ed26a17d1;hpb=c7b96d682958532c4eb2d5c2d81bb6ac342fd410
>>>
>>> Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
>>> ---
>>>    .../m4/{m4-1.4.20.inc => m4-1.4.21.inc}       |   5 +-
>>>    ...4-native_1.4.20.bb => m4-native_1.4.21.bb} |   0
>>>    ...gcc-Wformat-security-warnings-with-d.patch | 133 ------------------
>>>    .../m4/{m4_1.4.20.bb => m4_1.4.21.bb}         |   0
>>>    4 files changed, 2 insertions(+), 136 deletions(-)
>>>    rename meta/recipes-devtools/m4/{m4-1.4.20.inc => m4-1.4.21.inc} (90%)
>>>    rename meta/recipes-devtools/m4/{m4-native_1.4.20.bb => m4-native_1.4.21.bb} (100%)
>>>    delete mode 100644 meta/recipes-devtools/m4/m4/0001-gettext-h-Avoid-gcc-Wformat-security-warnings-with-d.patch
>>>    rename meta/recipes-devtools/m4/{m4_1.4.20.bb => m4_1.4.21.bb} (100%)
>>>
>>> diff --git a/meta/recipes-devtools/m4/m4-1.4.20.inc b/meta/recipes-devtools/m4/m4-1.4.21.inc
>>> similarity index 90%
>>> rename from meta/recipes-devtools/m4/m4-1.4.20.inc
>>> rename to meta/recipes-devtools/m4/m4-1.4.21.inc
>>> index 5c4ba09288..ce9fe2be8e 100644
>>> --- a/meta/recipes-devtools/m4/m4-1.4.20.inc
>>> +++ b/meta/recipes-devtools/m4/m4-1.4.21.inc
>>> @@ -7,19 +7,18 @@ GNU M4 also has built-in functions for including files, running shell commands,
>>>    inherit autotools texinfo ptest gettext
>>>
>>>    SRC_URI = "${GNU_MIRROR}/m4/m4-${PV}.tar.gz \
>>> -           file://0001-gettext-h-Avoid-gcc-Wformat-security-warnings-with-d.patch \
>>>               "
>>>    SRC_URI:append:class-target = " file://run-ptest \
>>>                                    file://0001-test-c32ispunct-Check-for-musl-along-with-glibc.patch \
>>>                                    file://serial-tests-config.patch \
>>>                                  "
>>>
>>> -SRC_URI[sha256sum] = "6ac4fc31ce440debe63987c2ebbf9d7b6634e67a7c3279257dc7361de8bdb3ef"
>>> +SRC_URI[sha256sum] = "38ae59f7a30bf9c108193cc5c25fbb06014f21e230c7ede2eff614f7b7c37ed8"
>>>
>>>    LICENSE = "GPL-3.0-only"
>>>
>>>    LIC_FILES_CHKSUM = "file://COPYING;md5=1ebbd3e34237af26da5dc08a4e440464\
>>> -                 file://examples/COPYING;md5=4031593b2166d6c47cae282d944a7ede"
>>> +                 file://examples/COPYING;md5=005f2e201a0526c1d1d79dd6303ecf23"
>>
>> There are new license in the example files barem4.m4 and testbarem4.m4, it just
>> says "This program is distributed under a Creative Commons Share-alike license",
>> but not version is specified, I guess we should use CC-BY-SA-4.0.
> 
> Is there an option to install the examples? I've checked the build and
> image directories and the examples aren't built nor installed.

Sorry, I didn't know that either. I found this issue during update m4, thanks
for working on it.

// Robert





      reply	other threads:[~2026-03-11  5:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 18:03 [PATCH 1/3] m4: upgrade to 1.4.21 martin.jansa
2026-03-05 18:03 ` [PATCH 2/3] dtc: backport fix for build with glibc-2.43 martin.jansa
2026-03-05 18:03 ` [PATCH 3/3] libunistring: upgrade to 1.4.2 martin.jansa
2026-03-07 15:00 ` [OE-core] [PATCH 1/3] m4: upgrade to 1.4.21 Robert Yang
2026-03-08 12:14   ` Martin Jansa
2026-03-11  5:17     ` Robert Yang [this message]

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=98cccb05-390e-4362-899c-8eace203e970@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox