All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 1/3] glibc: Upgrade to 2.35 (RFC)
Date: Wed, 09 Feb 2022 13:48:01 +0000	[thread overview]
Message-ID: <038723a3f16f3260abafc5e6f60bc780f91b5328.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220208225310.1685131-1-raj.khem@gmail.com>

On Tue, 2022-02-08 at 14:53 -0800, Khem Raj wrote:
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> 
> Package /usr/bin/ld.so in a separate package
> 
> ld.so is a new tool which is added as a symlink to original dynamic
> linker so make it available with same name across architectures which is
> useful to leveral features like  --preload, --audit, and --list-diagnostics
> more accessible to end users
> 

There is still a QA error with this for multilib:

https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/4735/steps/11/logs/stdio

Cheers,

Richard






  parent reply	other threads:[~2022-02-09 13:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 22:53 [PATCH v3 1/3] glibc: Upgrade to 2.35 (RFC) Khem Raj
2022-02-08 22:53 ` [PATCH v3 2/3] meta: Remove libsegfault and catchsegv Khem Raj
2022-02-08 22:53 ` [PATCH v3 3/3] perl: Help resolving WNOHANG and _exit in Posix module Khem Raj
2022-02-09 13:48 ` Richard Purdie [this message]
2022-02-09 17:36   ` [PATCH v3 1/3] glibc: Upgrade to 2.35 (RFC) Khem Raj
2022-02-15  8:25 ` [OE-core] " Jia, Hongxu
2022-02-15 13:37   ` Richard Purdie
2022-02-15 16:17   ` Khem Raj
2022-02-16  2:28     ` Jia, Hongxu
2022-02-16  4:08       ` Khem Raj
2022-02-16  8:31         ` Jia, Hongxu
2022-02-16  9:22           ` Martin Jansa
2022-02-17  1:41             ` Mittal, Anuj
2022-02-17 22:46               ` Richard Purdie
2022-02-17 22:38       ` Richard Purdie

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=038723a3f16f3260abafc5e6f60bc780f91b5328.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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.