> Is it safe to backport to morty, which doesn't have RSS?

It doesn't work well for me, all the builds are now failing with:

ERROR: glibc-2.24-r0 do_stash_locale_setscene: The recipe glibc is trying
to install files into a shared area when those files already exist. Those
files and their manifest location are:
   TMPDIR/sysroots-components/aarch64/glibc-stash-locale/SUPPORTED
 Matched in b''
   TMPDIR/
sysroots-components/aarch64/glibc-stash-locale/lib/libnss_nisplus.so.2
 Matched in b''
   TMPDIR/sysroots-components/aarch64/glibc-stash-locale/lib/ld-2.24.so
 Matched in b''
...



On Thu, Apr 5, 2018 at 11:41 PM, Andre McCurdy <armccu...@gmail.com> wrote:

> On Thu, Apr 5, 2018 at 6:53 AM, Armin Kuster <akuster...@gmail.com> wrote:
> > Please consider these changes for Morty. Clean AB build
> >
> > This included sdk locale and host glibc 2.27 fixes.
> >
> > The following changes since commit 34b26ec18450a3bc72f7b8a0f2df0b
> faae1140dd:
> >
> >   linux-firmware: Add reference to iwlwifi-8000C firmware (2018-03-19
> 15:58:33 +0000)
> >
> > are available in the git repository at:
> >
> >   git://git.yoctoproject.org/poky-contrib stable/morty-next
> >   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=
> stable/morty-next
> >
> > Richard Purdie (4):
> >   lib/oe/package_manager/sdk: Ensure do_populate_sdk_ext and
> >     do_populate_sdk repos don't conflict
> >   glibc: Separate locale files to their own sstate task
>
> This commit comes with the comment:
>
>     Putting the locale and script files into the sysroot for use by their
>     specific recipes used to be a simple way to share the files. With RSS,
>     we don't want to copy these into many different recipes so put these
>     files in their own sstate task.
>
> Is it safe to backport to morty, which doesn't have RSS?
>
> >   image/packagegroup/populate_sdk: Drop do_populate_sysroot task
> >     properly
> >   glibc-package: Avoid race sstate races with do_stash_locale
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to