On 04/06/2020 22.05, Andre McCurdy wrote:
> but I can try to summarise the details related to the actual patch...
[snip]
> There's a genuine bug and I don't see an obviously better fix, so I
> think the patch should be merged.
Thank you for that summary, that's much better than what I could hav
On Thu, Jun 04, 2020 at 01:05:30PM -0700, Andre McCurdy wrote:
> The fix being proposed is simply to always leave the config file in
> the rootfs, so it's always there when ldconfig is run at build time.
> Doing so seems safe enough. Since the config file is only parsed by
> ldconfig, there's no ru
On Thu, Jun 4, 2020 at 5:43 AM Richard Purdie
wrote:
> On Wed, 2020-06-03 at 13:44 -0700, Andre McCurdy wrote:
> > On Wed, Jun 3, 2020 at 12:38 AM Rasmus Villemoes
> > wrote:
> > > On 02/06/2020 23.46, Andre McCurdy wrote:
> > > > On Tue, Jun 2, 2020 at 2:15 PM Phil Blundell via
> > > > lists.ope
On Wed, 2020-06-03 at 13:44 -0700, Andre McCurdy wrote:
> On Wed, Jun 3, 2020 at 12:38 AM Rasmus Villemoes
> wrote:
> > On 02/06/2020 23.46, Andre McCurdy wrote:
> > > On Tue, Jun 2, 2020 at 2:15 PM Phil Blundell via
> > > lists.openembedded.org
> > > wrote:
> > > > On Tue, Jun 02, 2020 at 09:17:
On 03/06/2020 22.44, Andre McCurdy wrote:
> On Wed, Jun 3, 2020 at 12:38 AM Rasmus Villemoes
> wrote:
>> On 02/06/2020 23.46, Andre McCurdy wrote:
>>> On Tue, Jun 2, 2020 at 2:15 PM Phil Blundell via
>>> lists.openembedded.org wrote:
>>>
>>> It seems like a weird corner case to me. Where do
On Tue, Jun 2, 2020 at 2:46 PM Andre McCurdy wrote:
>
> On Tue, Jun 2, 2020 at 2:15 PM Phil Blundell via
> lists.openembedded.org wrote:
> >
> > 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 d
On Wed, Jun 3, 2020 at 12:38 AM Rasmus Villemoes
wrote:
> On 02/06/2020 23.46, Andre McCurdy wrote:
> > On Tue, Jun 2, 2020 at 2:15 PM Phil Blundell via
> > lists.openembedded.org wrote:
> >>
> >> On Tue, Jun 02, 2020 at 09:17:44PM +0100, Richard Purdie wrote:
> >>> I understand the concern, I am
On 02/06/2020 23.46, Andre McCurdy wrote:
> On Tue, Jun 2, 2020 at 2:15 PM Phil Blundell via
> lists.openembedded.org wrote:
>>
>> 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 a
On 02/06/2020 23.15, Phil Blundell wrote:
> 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
On Tue, Jun 2, 2020 at 2:15 PM Phil Blundell via
lists.openembedded.org wrote:
>
> 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
> > m
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 c
On Tue, 2020-06-02 at 22:00 +0200, Phil Blundell wrote:
> On Tue, Jun 02, 2020 at 02:17:22PM +0200, Rasmus Villemoes wrote:
> > In case of a read-only rootfs, one could add some logic to remove
> > them
> > if one really wants to shave those few dozens of bytes off.
>
> Note that there's also a sl
On Tue, Jun 02, 2020 at 02:17:22PM +0200, Rasmus Villemoes wrote:
> In case of a read-only rootfs, one could add some logic to remove them
> if one really wants to shave those few dozens of bytes off.
Note that there's also a slight runtime performance penalty associated
with having these files in
On 02/06/2020 19.58, Khem Raj wrote:
> On Tue, Jun 2, 2020 at 5:17 AM Rasmus Villemoes
> wrote:
>>
>> There are cases where one doesn't want ldconfig on target (e.g. for
>> read-only root filesystems, it's rather pointless), yet one still
>> needs ld.so.conf to be present at image build time:
>>
>
On Tue, Jun 2, 2020 at 5:17 AM Rasmus Villemoes
wrote:
>
> There are cases where one doesn't want ldconfig on target (e.g. for
> read-only root filesystems, it's rather pointless), yet one still
> needs ld.so.conf to be present at image build time:
>
> When some recipe installs libraries to a non-
There are cases where one doesn't want ldconfig on target (e.g. for
read-only root filesystems, it's rather pointless), yet one still
needs ld.so.conf to be present at image build time:
When some recipe installs libraries to a non-standard location, and
dutifully drops in a file in /etc/ld.so.conf
16 matches
Mail list logo
