On Thu, Jul 04, 2019 at 06:57:50AM -0500, Jason Wessel wrote:
> On 7/4/19 5:57 AM, Adrian Bunk wrote:
> > On Thu, Jul 04, 2019 at 11:13:18AM +0200, Martin Jansa wrote:
> > > I don't see how this change (or the previous glibc-locale one) would cause
> > > that, but since the oe-core upgrade yesterday I'm seeing following
> > > glibc-locale.do_package failure:
> > > http://errors.yoctoproject.org/Errors/Details/250557/
> > > 
> > > DEBUG: Executing shell function do_prep_locale_tree
> > > tar: i18n: Cannot stat: No such file or directory
> > > tar: Exiting with failure status due to previous errors
> > > gzip:
> > > TOPDIR/tmp-glibc/work/core2-64-oe-linux/glibc-locale/2.29-r0/locale-tree//usr/share/i18n/charmaps/*gz.gz:
> > > No such file or directory
> > > WARNING:
> > > TOPDIR/tmp-glibc/work/core2-64-oe-linux/glibc-locale/2.29-r0/temp/run.do_prep_locale_tree.23303:1
> > > exit 1 from 'gunzip $i'
> > > 
> > > anyone else seeing this?
> > 
> > Yes.
> 
> 
> I don't know that it was specifically this change that causes the problem but 
> rather any change to this function.   If that is not the case can either of 
> you send me your local.conf file, and I'll try to reproduce it.  If the 
> following doesn't work around the problem, there is clearly another corner 
> case that is not well understood.
> 
> bitbake -c cleansstate glibc glibc-locale
>...

bitbake -c cleansstate glibc glibc-locale nativesdk-glibc nativesdk-glibc-locale

This seems to workaround the problem in the cases I have seen so far,
so what you said about the cause looks plausible to me.

> Cheers,
> 
> Jason.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to