All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Phil Blundell" <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	openembedded-core@lists.openembedded.org,
	Martin Jansa <martin.jansa@gmail.com>,
	Khem Raj <raj.khem@gmail.com>,
	Andreas Oberritter <obi@opendreambox.org>
Subject: Re: [OE-core] [PATCH v3] glibc: move ld.so.conf back to main package
Date: Tue, 2 Jun 2020 23:15:24 +0200	[thread overview]
Message-ID: <20200602211524.GC2207@pbcl.net> (raw)
In-Reply-To: <24a52dc42bb9eb49e2f8802a3c7558859160de18.camel@linuxfoundation.org>

On Tue, Jun 02, 2020 at 09:17:44PM +0100, Richard Purdie wrote:
> I understand the concern, I am a little torn on this as adding in too
> many different controls and options complicates the test matrix and
> makes things harder for users.
> 
> You're effectively suggesting a new DISTRO_FEATURE to control this? or
> maybe better, perhaps a glibc PACKAGECONFIG?

Yes, right.  I don't think it need be a DISTRO_FEATURE because nothing
outside glibc needs to care.

Here are the scenarios that I think matter, ordered from simplest to
most complex:

1. Immutable filesystem, every library installed in the place where
ld.so would first look for it anyway (i.e. everything in {/usr}/lib).
In this case, we don't want ldconfig (because it can never do anything
useful), we don't want ld.so.cache and we don't want ld.so.conf
because they would cause ld.so to do extra file loads and computation
but end up with the same result that it would anyway.

2. Immutable filesystem but some libraries are in places that ld.so
wouldn't automatically know about.  In this case we do want ld.so.conf
and ld.so.cache, but we still don't want ldconfig.

3. Mutable filesystem where arbitrary binaries can be installed in
arbitrary places.  It's probably debatable whether ldconfig is needed
in all these cases, but clearly it's needed in some and I think at
this point it can be left to a DISTRO decision how exactly they want
to optimize things.

I think right now oe-core supports #1 and #3.  The proposed patch
seems to be aimed at #2, which is a completely valid usecase, but
my concern is that we don't want to pessimize #1 in the process.

There is a whole parallel discussion to be had about the merits
or otherwise of ld.so's hwcaps mechanism.  meta-micro has been
carrying a patch for about a decade to turn all that stuff off,
on the grounds that it's just a loss on any kind of embedded
environment.  Maybe I should make some effort to get it upstream
as an option.

p.


  reply	other threads:[~2020-06-02 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1614B0E5E96C4272.14405@lists.openembedded.org>
2020-06-02 12:17 ` [PATCH v3] glibc: move ld.so.conf back to main package Rasmus Villemoes
2020-06-02 17:58   ` Khem Raj
2020-06-02 19:56     ` Rasmus Villemoes
2020-06-02 20:00   ` [OE-core] " Phil Blundell
2020-06-02 20:17     ` Richard Purdie
2020-06-02 21:15       ` Phil Blundell [this message]
2020-06-02 21:46         ` Andre McCurdy
2020-06-03  7:38           ` Rasmus Villemoes
2020-06-03 20:44             ` Andre McCurdy
2020-06-04  6:57               ` Rasmus Villemoes
2020-06-04 12:43               ` Richard Purdie
2020-06-04 20:05                 ` Andre McCurdy
2020-06-04 21:04                   ` Phil Blundell
2020-06-05 10:34                   ` Rasmus Villemoes
2020-06-03 23:41           ` Khem Raj
2020-06-03  7:17         ` Rasmus Villemoes

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=20200602211524.GC2207@pbcl.net \
    --to=pb@pbcl.net \
    --cc=martin.jansa@gmail.com \
    --cc=obi@opendreambox.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=richard.purdie@linuxfoundation.org \
    /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.