From: Adrian Bunk <bunk@stusta.de>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] glibc/glibc-locale: Fix do_stash_locale to work with usrmerge and multilibs
Date: Sat, 6 Jul 2019 22:31:29 +0300 [thread overview]
Message-ID: <20190706193129.GD1877@localhost> (raw)
In-Reply-To: <20567801-7441-e67a-59f0-e492ef60bacb@windriver.com>
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
next prev parent reply other threads:[~2019-07-06 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 20:16 [PATCH 0/3] Fixes for build failures for multilibs + usrmerge, NLS and GCONV Jason Wessel
2019-07-02 20:16 ` [PATCH 1/3] psmisc: Fix dependency for USE_NLS=no Jason Wessel
2019-07-02 20:16 ` [PATCH 2/3] glibc-locale: Fix build error with PACKAGE_NO_GCONV = "1" Jason Wessel
2019-07-02 20:16 ` [PATCH 3/3] glibc/glibc-locale: Fix do_stash_locale to work with usrmerge and multilibs Jason Wessel
2019-07-04 9:13 ` Martin Jansa
2019-07-04 10:57 ` Adrian Bunk
2019-07-04 11:57 ` Jason Wessel
2019-07-06 19:31 ` Adrian Bunk [this message]
2019-07-08 19:21 ` Jason Wessel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190706193129.GD1877@localhost \
--to=bunk@stusta.de \
--cc=jason.wessel@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox