From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] support/{config-fragments, testing}: select INET_RPC option for custom glibc external toolchains
Date: Tue, 29 Dec 2020 22:06:26 +0100 [thread overview]
Message-ID: <20201229220626.4d99ccdc@windsurf> (raw)
In-Reply-To: <20201207204821.3588178-4-romain.naour@gmail.com>
On Mon, 7 Dec 2020 21:48:20 +0100
Romain Naour <romain.naour@gmail.com> wrote:
> The sun rpc support has been removed from glibc 2.32 [1], so BR2_TOOLCHAIN_EXTERNAL_INET_RPC
> will no longer be enabled by default for custom external toolchains.
>
> Add this option in config fragments used by autobuild and testing scripts.
>
> [1] https://sourceware.org/pipermail/libc-announce/2020/000029.html
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> support/config-fragments/autobuild/bootlin-x86-64-glibc.config | 1 +
> support/config-fragments/autobuild/br-aarch64-glibc.config | 1 +
> .../config-fragments/autobuild/br-arm-cortex-a9-glibc.config | 1 +
> .../config-fragments/autobuild/br-mips32r6-el-hf-glibc.config | 1 +
> .../config-fragments/autobuild/br-mips64r6-el-hf-glibc.config | 1 +
> support/config-fragments/autobuild/br-nios2-glibc.config | 1 +
> .../config-fragments/autobuild/br-powerpc64-power7-glibc.config | 1 +
> .../autobuild/br-powerpc64le-power8-glibc.config | 1 +
> support/config-fragments/autobuild/br-riscv32.config | 1 +
> support/config-fragments/autobuild/br-riscv64.config | 1 +
> support/config-fragments/autobuild/br-sparc64-glibc.config | 1 +
> support/testing/tests/boot/test_syslinux.py | 2 ++
> support/testing/tests/core/test_hardening.py | 1 +
> support/testing/tests/package/test_glxinfo.py | 1 +
> 14 files changed, 15 insertions(+)
We are going to keep BR2_TOOLCHAIN_EXTERNAL_INET_RPC default to yes
with glibc for the moment, so I've marked this patch as Rejected.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-12-29 21:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 20:48 [Buildroot] [PATCH 1/5] package/ogre: bump to version 1.12.9 Romain Naour
2020-12-07 20:48 ` [Buildroot] [PATCH 2/5] support/scripts/gen-bootlin-toolchains: riscv32 use a pre-2.33 glibc version without RPC support Romain Naour
2020-12-07 21:50 ` Thomas Petazzoni
2020-12-07 22:30 ` Romain Naour
2020-12-08 10:55 ` Thomas Petazzoni
2020-12-29 21:05 ` Thomas Petazzoni
2020-12-07 20:48 ` [Buildroot] [PATCH 3/5] toolchain/toolchain-external/toolchain-external-bootlin: regenerate for riscv32 toolchain Romain Naour
2020-12-29 21:05 ` Thomas Petazzoni
2020-12-07 20:48 ` [Buildroot] [PATCH 4/5] support/{config-fragments, testing}: select INET_RPC option for custom glibc external toolchains Romain Naour
2020-12-07 21:52 ` Thomas Petazzoni
2020-12-07 22:33 ` Romain Naour
2020-12-29 21:06 ` Thomas Petazzoni [this message]
2020-12-07 20:48 ` [Buildroot] [PATCH 5/5] package/glibc: bump to version 2.32-23-g050022910be1d1f5c11cd5168f1685ad4f9580d2 Romain Naour
2020-12-29 22:34 ` Yann E. MORIN
2020-12-29 22:37 ` Thomas Petazzoni
2020-12-29 22:22 ` [Buildroot] [PATCH 1/5] package/ogre: bump to version 1.12.9 Thomas Petazzoni
2021-01-04 21:02 ` Romain Naour
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=20201229220626.4d99ccdc@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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 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.