Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] musl-obstack: upgrade 1.1 -> 1.2
Date: Wed, 15 Jun 2022 16:16:03 +0800	[thread overview]
Message-ID: <1655280963-6605-4-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1655280963-6605-1-git-send-email-wangmy@fujitsu.com>

Changelog:
=========
Use obstack.c and obstack.h from gcc-10.2.0 libiberty.
Add AC_CONFIG_HEADERS to configure.ac and make ./bootstrap.sh create config.h.in.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 meta/recipes-core/musl/musl-obstack.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/musl/musl-obstack.bb b/meta/recipes-core/musl/musl-obstack.bb
index 4df24c013b..5c95ddbc94 100644
--- a/meta/recipes-core/musl/musl-obstack.bb
+++ b/meta/recipes-core/musl/musl-obstack.bb
@@ -8,8 +8,8 @@ LICENSE = "GPL-2.0-or-later"
 LIC_FILES_CHKSUM = "file://COPYING;md5=3d23e4eef8243efcaab6f0a438078932"
 SECTION = "libs"
 
-PV = "1.1"
-SRCREV = "d2ad66b0df44a4b784956f7f7f2717131ddc05f4"
+PV = "1.2"
+SRCREV = "466f773fe171da427e28be79b9cf48ccfddfb7e2"
 SRC_URI = "git://github.com/pullmoll/musl-obstack;branch=master;protocol=https"
 
 UPSTREAM_CHECK_COMMITS = "1"
-- 
2.25.1



      parent reply	other threads:[~2022-06-15  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  8:16 [OE-core] [PATCH] lighttpd: upgrade 1.4.64 -> 1.4.65 Wang Mingyu
2022-06-15  8:16 ` [OE-core] [PATCH] erofs-utils: upgrade 1.4 -> 1.5 Wang Mingyu
2022-06-15  8:32   ` Alexander Kanavin
2022-06-15  8:39     ` Alexander Kanavin
2022-06-15  8:16 ` [OE-core] [PATCH] gnu-config: update to latest version Wang Mingyu
2022-06-15  8:16 ` Wang Mingyu [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=1655280963-6605-4-git-send-email-wangmy@fujitsu.com \
    --to=wangmy@fujitsu.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