On Wed, 2021-08-18 at 06:42 -0700, Khem Raj wrote:
>
>
> On Wed, Aug 18, 2021 at 12:00 AM Richard Purdie
> wrote:
> > On Tue, 2021-08-17 at 17:40 -0700, Khem Raj wrote:
> > > hmm I am seeing pseudo build failures on master-next on all arches see
> > > [1]. I wonder if this is related
> > >
>
On Wed, Aug 18, 2021 at 12:00 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2021-08-17 at 17:40 -0700, Khem Raj wrote:
> > hmm I am seeing pseudo build failures on master-next on all arches see
> > [1]. I wonder if this is related
> >
> >
On Tue, 2021-08-17 at 17:40 -0700, Khem Raj wrote:
> hmm I am seeing pseudo build failures on master-next on all arches see
> [1]. I wonder if this is related
>
> https://errors.yoctoproject.org/Errors/Details/601473/
I think that would be an issue with my patch in master-next to try and fix
hmm I am seeing pseudo build failures on master-next on all arches see
[1]. I wonder if this is related
https://errors.yoctoproject.org/Errors/Details/601473/
On Tue, Aug 17, 2021 at 4:46 PM Khem Raj wrote:
>
> On Tue, Aug 17, 2021 at 3:29 PM Ross Burton wrote:
> >
> > In glibc 2.34, the
On Tue, Aug 17, 2021 at 3:29 PM Ross Burton wrote:
>
> In glibc 2.34, the libraries libpthread, libdl, libutil, libanl have
> been integrated into libc. To retain compatibility with old binaries the
> shared libaries are still shipped but are empty, and to keep software
> building there are empty
In glibc 2.34, the libraries libpthread, libdl, libutil, libanl have
been integrated into libc. To retain compatibility with old binaries the
shared libaries are still shipped but are empty, and to keep software
building there are empty static libraries.
However, these static libraries get
