From: <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <alex.kanavin@gmail.com>
Subject: [PATCH v3 0/2] automake: 1.17 -> 1.18.1
Date: Wed, 3 Sep 2025 20:40:37 -0700 [thread overview]
Message-ID: <cover.1756957117.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
* V3
- Upgarde to 1.18.1 (v2 is 1.18)
* V2:
- Drop 0001-configure-don-t-report-error-when-the-path-of-Perl-c.patch as Ross
suggested.
- Take a pull request from github to fix libcheck's build error with automake
1.18.1.
* V1
- Initial version
// Robert
The following changes since commit 0a849dc7edeecb6c16a8a0fe347015d6d85e9dfd:
vte: upgrade 0.78.2 -> 0.80.3 (2025-09-01 23:07:03 +0100)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/pu
https://github.com/robertlinux/yocto/tree/rbt/pu
Robert Yang (2):
automake: 1.17 -> 1.18.1
libcheck: Fix do_install error with automake 1.18.1
...report-error-when-the-path-of-Perl-c.patch | 34 -----------
.../{automake_1.17.bb => automake_1.18.1.bb} | 3 +-
...0001-Fix-texinfo-errors-and-warnings.patch | 60 +++++++++++++++++++
.../libcheck/libcheck_0.15.2.bb | 5 +-
4 files changed, 65 insertions(+), 37 deletions(-)
delete mode 100644 meta/recipes-devtools/automake/automake/0001-configure-don-t-report-error-when-the-path-of-Perl-c.patch
rename meta/recipes-devtools/automake/{automake_1.17.bb => automake_1.18.1.bb} (85%)
create mode 100644 meta/recipes-support/libcheck/libcheck/0001-Fix-texinfo-errors-and-warnings.patch
--
2.49.0
next reply other threads:[~2025-09-04 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 3:40 liezhi.yang [this message]
2025-09-04 3:40 ` [PATCH v3 1/2] automake: 1.17 -> 1.18.1 liezhi.yang
2025-09-04 3:40 ` [PATCH v3 2/2] libcheck: Fix do_install error with automake 1.18.1 liezhi.yang
2025-09-04 3:46 ` Patchtest results for " patchtest
2025-09-09 17:36 ` [OE-core] [PATCH v3 0/2] automake: 1.17 -> 1.18.1 Ross Burton
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=cover.1756957117.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=alex.kanavin@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