public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Clément Péron" <peron.clem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: "Clément Péron" <peron.clem@gmail.com>
Subject: [RFC PATCH 0/4] Bump Protobuf/gRPC
Date: Thu, 20 Jul 2023 18:22:58 +0200	[thread overview]
Message-ID: <20230720162535.116519-1-peron.clem@gmail.com> (raw)

Hi,

I'm trying to bump gRPC to a more recent version,
but it requires a bump of protobuf.

I'm strugling with the following issue when compiling:

ERROR: abseil-cpp-20230125.3-r0 do_package: Variable Requires: absl_config = 20230125, absl_core_headers = 20230125, absl_log_internal_append_truncated = 20230125, absl_log_internal_config = 20230125, absl_log_internal_globals = 20230125, absl_log_severity = 20230125, absl_strings = 20230125, absl_str_format = 20230125, absl_time = 20230125, absl_span  contains an operation using the old override syntax. Please convert this layer/metadata before attempting to use with a newer bitbake.
ERROR: Logfile of failure stored in: /build/tmp/work/armv8a-poky-linux/abseil-cpp/20230125.3-r0/temp/log.do_package.2192204
ERROR: Task (/build/../meta-outsight/recipes-devtools/abseil-cpp/abseil-cpp_git.bb:do_package) failed with exit code '1'

Do you have an idea of what is happening?

Thanks for your help

Clément Péron (4):
  jsoncpp: extend with nativesdk
  devtools: protobuf: add utf8-range recipe
  protobuf: bump to 3.23.4
  devtools: grpc: bump to 1.56.2

 ...RPCPP_ABSEIL_SYNC-to-GPR_ABSEIL_SYNC.patch | 62 -------------
 ...d-separate-export-for-plugin-targets.patch | 93 -------------------
 .../grpc/{grpc_1.50.1.bb => grpc_1.56.2.bb}   |  6 +-
 .../recipes-devtools/jsoncpp/jsoncpp_1.9.5.bb |  2 +-
 .../0001-Fix-linking-error-with-ld-gold.patch | 69 --------------
 ...e-respect-CXX-LDFLAGS-variables-fix-.patch |  4 +-
 ...protobuf_3.21.12.bb => protobuf_3.23.4.bb} |  8 +-
 .../protobuf/utf8-range_git.bb                | 22 +++++
 8 files changed, 32 insertions(+), 234 deletions(-)
 delete mode 100644 meta-oe/recipes-devtools/grpc/grpc/0001-Revert-Changed-GRPCPP_ABSEIL_SYNC-to-GPR_ABSEIL_SYNC.patch
 delete mode 100644 meta-oe/recipes-devtools/grpc/grpc/0001-cmake-add-separate-export-for-plugin-targets.patch
 rename meta-oe/recipes-devtools/grpc/{grpc_1.50.1.bb => grpc_1.56.2.bb} (92%)
 delete mode 100644 meta-oe/recipes-devtools/protobuf/protobuf/0001-Fix-linking-error-with-ld-gold.patch
 rename meta-oe/recipes-devtools/protobuf/{protobuf_3.21.12.bb => protobuf_3.23.4.bb} (95%)
 create mode 100644 meta-oe/recipes-devtools/protobuf/utf8-range_git.bb

-- 
2.41.0



             reply	other threads:[~2023-07-20 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 16:22 Clément Péron [this message]
2023-07-20 16:22 ` [RFC PATCH 1/4] jsoncpp: extend with nativesdk Clément Péron
2023-07-20 16:23 ` [RFC PATCH 2/4] devtools: protobuf: add utf8-range recipe Clément Péron
2023-07-20 16:23 ` [RFC PATCH 3/4] protobuf: bump to 3.23.4 Clément Péron
2023-07-20 16:23 ` [RFC PATCH 4/4] devtools: grpc: bump to 1.56.2 Clément Péron
2023-07-20 16:38 ` [OE-core] [RFC PATCH 0/4] Bump Protobuf/gRPC Martin Jansa
2023-07-21  9:07   ` Clément Péron
     [not found]   ` <1773D6CEC3F30D4C.21241@lists.openembedded.org>
2023-07-22 10:11     ` Clément Péron

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=20230720162535.116519-1-peron.clem@gmail.com \
    --to=peron.clem@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