On Thursday 21 February 2019 at 13:01:27 +, Richard Purdie wrote:
> On Wed, 2019-02-20 at 16:47 +, Mike Crowe wrote:
> > On Wednesday 23 January 2019 at 16:27:59 +, Mike Crowe wrote:
> > >
> > > Does the lack of response mean that both approaches are horrendous?
> > > If so, do you
On Wed, 2019-02-20 at 16:47 +, Mike Crowe wrote:
> On Wednesday 23 January 2019 at 16:27:59 +, Mike Crowe wrote:
> >
> > Does the lack of response mean that both approaches are horrendous?
> > If so, do you have any better ideas?
>
> There doesn't seem to be much interest in this one.
>
On Wednesday 23 January 2019 at 16:27:59 +, Mike Crowe wrote:
> On Friday 11 January 2019 at 16:59:44 +, Mike Crowe wrote:
> > On Friday 11 January 2019 at 16:53:47 +, Richard Purdie wrote:
> > > On Fri, 2019-01-11 at 16:49 +, Mike Crowe wrote:
> > > > Until now, glibc was
On Friday 11 January 2019 at 16:59:44 +, Mike Crowe wrote:
> On Friday 11 January 2019 at 16:53:47 +, Richard Purdie wrote:
> > On Fri, 2019-01-11 at 16:49 +, Mike Crowe wrote:
> > > Until now, glibc was responsible for creating an AArch64 dynamic
> > > loader symlink if required for
On Friday 11 January 2019 at 16:53:47 +, Richard Purdie wrote:
> On Fri, 2019-01-11 at 16:49 +, Mike Crowe wrote:
> > Until now, glibc was responsible for creating an AArch64 dynamic
> > loader symlink if required for ABI compatibility.
> >
> > Unfortunately, using multilib with AArch64
On Fri, 2019-01-11 at 16:49 +, Mike Crowe wrote:
> Until now, glibc was responsible for creating an AArch64 dynamic
> loader symlink if required for ABI compatibility.
>
> Unfortunately, using multilib with AArch64 caused the rmdir in
> glibc-package.inc:do_poststash_install_cleanup to fail
Until now, glibc was responsible for creating an AArch64 dynamic loader
symlink if required for ABI compatibility.
Unfortunately, using multilib with AArch64 caused the rmdir in
glibc-package.inc:do_poststash_install_cleanup to fail because that task
did not expect to find the dynamic loader
