All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/glibc: bump to version 2.32-4-g69beb5cbf85cae1c61fe7432500ac10880dc7b07
Date: Sun, 15 Nov 2020 15:49:28 +0100	[thread overview]
Message-ID: <87ff0258-3abf-c8a5-e33c-234adeb2fe39@gmail.com> (raw)
In-Reply-To: <ca30d14c-6182-f97b-56c5-e206ed2839e2@gmail.com>

Hello Thomas,

Le 14/11/2020 ? 16:19, Romain Naour a ?crit?:
> Hello Thomas,
> 
> Sorry for my late reply...
> 
> Le 08/10/2020 ? 21:59, Thomas Petazzoni a ?crit?:
>> Hello Romain,
>>
>> On Fri,  2 Oct 2020 17:59:31 +0200
>> Romain Naour <romain.naour@gmail.com> wrote:
>>
>>> - Support for Synopsys ARC HS cores (ARCv2 ISA) running Linux has been added.
>>>   Remove the ARC specific version.
>>>
>>> - Remove --enable-obsolete-rpc configure option.
>>
>> If I read this, and upstream glibc commit
>> 5500cdba4018ddbda7909bc7f4f9718610b43cf0, it's not just the
>> --enable-obsolete-rpc flag that has been removed, but really all the
>> RPC code.
>>
>> Therefore, with glibc 2.32, this is no longer true:
>>
>> config BR2_TOOLCHAIN_BUILDROOT_GLIBC
>>         bool "glibc"
>> 	[...]
>>         # our glibc.mk enables RPC support
>>         select BR2_TOOLCHAIN_HAS_NATIVE_RPC
> 
> Indeed, we need to remove it.

I believe the change in the toolchain-external-custom is annoying

config BR2_TOOLCHAIN_EXTERNAL_INET_RPC
	bool "Toolchain has RPC support?"
	default y if BR2_TOOLCHAIN_EXTERNAL_GLIBC
	depends on !BR2_TOOLCHAIN_EXTERNAL_MUSL
	select BR2_TOOLCHAIN_HAS_NATIVE_RPC

We have to disable BR2_TOOLCHAIN_EXTERNAL_INET_RPC by default for glibc external
toolchains.

But currently most glibc toolchains in the wild still use a glibc < 2.32.

Best regards,
Romain

> 
>>
>> So to me, it seems like this needs a bit more work. Could you for
>> example try to build libnfs, with glibc 2.32, and libtirpc disabled ?
> 
> libnfs already select libtirpc when BR2_TOOLCHAIN_HAS_NATIVE_RPC is not set
> (musl or uclibc).
> So we can't use libnfs without BR2_TOOLCHAIN_HAS_NATIVE_RPC and libtirpc
> package. Each packages that require RPC seems to do the same.
> So, I don't think there is something to do at Buildroot level but we need to do
> some runtime testing (I hope libnfs is working with uclibc or musl :p ).
> 
> Best regards,
> Romain
> 
>>
>> Thanks,
>>
>> Thomas
>>
> 

  reply	other threads:[~2020-11-15 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 15:59 [Buildroot] [PATCH 1/2] package/localedef: bump to glibc-2.31-54 Romain Naour
2020-10-02 15:59 ` [Buildroot] [PATCH 2/2] package/glibc: bump to version 2.32-4-g69beb5cbf85cae1c61fe7432500ac10880dc7b07 Romain Naour
2020-10-02 21:57   ` Romain Naour
2020-10-04  9:45   ` Peter Korsgaard
2020-10-06 20:36     ` Romain Naour
2020-10-06 20:51       ` Peter Korsgaard
2020-10-08 19:59   ` Thomas Petazzoni
2020-11-14 15:19     ` Romain Naour
2020-11-15 14:49       ` Romain Naour [this message]
2020-11-16 21:17         ` [Buildroot] [PATCH 2/2] package/glibc: bump to version2.32-4-g69beb5cbf85cae1c61fe7432500ac10880dc7b07 Bernd Kuhls
2020-10-04  9:47 ` [Buildroot] [PATCH 1/2] package/localedef: bump to glibc-2.31-54 Peter Korsgaard
2020-10-10 19:40 ` Peter Korsgaard

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=87ff0258-3abf-c8a5-e33c-234adeb2fe39@gmail.com \
    --to=romain.naour@gmail.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.