From: "Andreas Oberritter" <obi@opendreambox.org>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Martin Jansa <martin.jansa@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Khem Raj <raj.khem@gmail.com>
Subject: Re: [PATCH] glibc: move ld.so.conf back to main package
Date: Mon, 18 May 2020 14:29:59 +0200 [thread overview]
Message-ID: <20200518142959.57fda0cc@opendreambox.org> (raw)
In-Reply-To: <0397befe-9f5d-a704-be07-00926fd3fffa@prevas.dk>
Hello Rasmus,
On Mon, 18 May 2020 14:12:43 +0200
Rasmus Villemoes <rasmus.villemoes@prevas.dk> wrote:
> I'm certainly open to other ways of solving this. But can we agree that
> it is a bug that the ldconfig done at build-time does not take
> /etc/ld.so.conf.d/* into account, and that that should not depend on
> whether one has ldconfig-the-binary on target?
have you tried installing ldconfig and adding it to ROOTFS_RO_UNNEEDED? It might be an improvement to include it in ROOTFS_RO_UNNEEDED by default.
Please consider use-cases where writable filesystems ship without ldconfig, but a user installs it from a package feed when needed.
Best regards,
Andreas
next prev parent reply other threads:[~2020-05-18 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 11:36 [PATCH] glibc: move ld.so.conf back to main package Rasmus Villemoes
2020-05-18 11:55 ` Martin Jansa
2020-05-18 12:12 ` Rasmus Villemoes
2020-05-18 12:23 ` [OE-core] " Phil Blundell
2020-05-18 12:29 ` Andreas Oberritter [this message]
2020-05-18 13:25 ` Rasmus Villemoes
2020-05-18 14:36 ` Andreas Oberritter
2020-06-02 9:44 ` [PATCH v2] " Rasmus Villemoes
2020-06-02 10:02 ` ✗ patchtest: failure for glibc: move ld.so.conf back to main package (rev2) Patchwork
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=20200518142959.57fda0cc@opendreambox.org \
--to=obi@opendreambox.org \
--cc=martin.jansa@gmail.com \
--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.