From: Yegor Yefremov via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: James Hilliard <james.hilliard1@gmail.com>
Subject: [Buildroot] [PATCH v2 0/2] package/{libabseil-cpp, python-grpcio}: disable for the MIPS n32 ABI
Date: Thu, 17 Sep 2026 13:37:18 +0200 [thread overview]
Message-ID: <20260917113720.1297345-1-yegorslists@gmail.com> (raw)
From: Yegor Yefremov <yegorslists@googlemail.com>
This is a v2 of "package/python-grpcio: disable for the MIPS n32 ABI":
https://patchwork.buildroot.org/project/buildroot/patch/20260908093538.2715153-1-yegorslists@gmail.com/
Changes v1 -> v2 (after Thomas' review):
- Added PATCH 1/2 fixing libabseil-cpp itself, which has exactly the
same problem. This automatically propagates to grpc, protobuf, re2,
webrtc-audio-processing, sysdig, falcosecurity-libs, collectd and
gst1-plugins-bad, which all already depend on
BR2_PACKAGE_LIBABSEIL_CPP_ARCH_SUPPORTS.
- Added the Fixes: tags (commit + autobuild result) to both patches.
- Documented since when the problem exists, with autobuild links on the
maintained branches, so that the LTS maintainers can decide about
backports. Short version: both are broken since mips64 was first
allowed, and both still need a backport to 2025.02.x; libabseil-cpp
also to 2026.02.x.
- Answered in the python-grpcio commit log why the Buildroot-provided
abseil cannot be used instead of the bundled one: grpcio's
GRPC_PYTHON_BUILD_SYSTEM_ABSL hardcodes /usr/include and globs
/usr/lib*/libabsl_*.so, so it is unusable when cross-compiling, and
it would not help here anyway since Buildroot's abseil has the same
limitation.
Note that n32 is the default ABI for BR2_mips64/BR2_mips64el, so this
covers the default mips64 autobuilder configurations. All in-tree mips64
defconfigs use n64 and are unaffected.
Tested with olddefconfig on mips64el n32 (both packages and their reverse
dependencies disappear), mips64el n64 and x86_64 (both still selectable).
Yegor Yefremov (2):
package/libabseil-cpp: disable for the MIPS n32 ABI
package/python-grpcio: disable for the MIPS n32 ABI
package/libabseil-cpp/Config.in | 4 ++++
package/python-grpcio/Config.in | 5 +++++
2 files changed, 9 insertions(+)
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-09-17 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 11:37 Yegor Yefremov via buildroot [this message]
2026-09-17 11:37 ` [Buildroot] [PATCH v2 1/2] package/libabseil-cpp: disable for the MIPS n32 ABI Yegor Yefremov via buildroot
2026-09-25 14:46 ` Raphaël Mélotte via buildroot
2026-09-17 11:37 ` [Buildroot] [PATCH v2 2/2] package/python-grpcio: " Yegor Yefremov via buildroot
2026-09-25 14:46 ` Raphaël Mélotte via buildroot
2026-09-18 7:37 ` [Buildroot] [PATCH v2 0/2] package/{libabseil-cpp, python-grpcio}: " Thomas Petazzoni via buildroot
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=20260917113720.1297345-1-yegorslists@gmail.com \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=yegorslists@googlemail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.