From: Michael Nosthoff <buildroot@heine.tech>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] bump grpc to 1.32.0
Date: Fri, 11 Sep 2020 18:34:06 +0200 [thread overview]
Message-ID: <20200911163409.25778-1-buildroot@heine.tech> (raw)
this series bumps grpc and its dependencies
- libabseil with two patchreleases
- protobuf 3.13
- grpc 1.32
Tested with grpc.config:
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_GRPC=y
on Ubuntu 20.04, gcc 9.3.0
./utils/test-pkg -c grpc.config -p grpc
br-arm-full [1/6]: OK
br-arm-cortex-a9-glibc [2/6]: OK
br-arm-cortex-m4-full [3/6]: SKIPPED
br-x86-64-musl [4/6]: OK
br-arm-full-static [5/6]: SKIPPED
sourcery-arm [6/6]: OK
Michael Nosthoff (3):
package/libabseil-cpp: bump to 20200225.2
package/{protobuf, python-protobuf}: bump to version 3.13.0
package/grpc: bump version to 1.32.0
.../grpc/0001-target-build-using-host-plugin.patch | 4 ++--
...-detect-the-availability-of-pthread_setname_.patch | 4 ++--
package/grpc/grpc.hash | 2 +-
package/grpc/grpc.mk | 11 ++++++-----
package/libabseil-cpp/libabseil-cpp.hash | 2 +-
package/libabseil-cpp/libabseil-cpp.mk | 2 +-
package/protobuf/protobuf.hash | 2 +-
package/protobuf/protobuf.mk | 6 +++---
package/python-protobuf/Config.in | 2 +-
package/python-protobuf/python-protobuf.hash | 2 +-
10 files changed, 19 insertions(+), 18 deletions(-)
--
2.25.1
next reply other threads:[~2020-09-11 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 16:34 Michael Nosthoff [this message]
2020-09-11 16:34 ` [Buildroot] [PATCH v2 1/3] package/libabseil-cpp: bump to 20200225.2 Michael Nosthoff
2020-09-19 19:53 ` Thomas Petazzoni
2020-09-11 16:34 ` [Buildroot] [PATCH v2 2/3] package/{protobuf, python-protobuf}: bump to version 3.13.0 Michael Nosthoff
2020-09-11 16:34 ` [Buildroot] [PATCH v2 3/3] package/grpc: bump version to 1.32.0 Michael Nosthoff
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=20200911163409.25778-1-buildroot@heine.tech \
--to=buildroot@heine.tech \
--cc=buildroot@busybox.net \
/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