From: Joshua Watt <jpewhacker@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] glibc: Fix locale DEPENDS
Date: Wed, 28 Aug 2019 11:27:32 -0500 [thread overview]
Message-ID: <8cd4e5be-e226-a297-daca-1cce33f5af31@gmail.com> (raw)
In-Reply-To: <893793eb5d13e0da6f32b446bb876ab562cd8f52.camel@linuxfoundation.org>
On 8/28/19 11:09 AM, Richard Purdie wrote:
> On Tue, 2019-08-27 at 07:45 -0500, Joshua Watt wrote:
>> gettext is required to generate the glibc locales in do_compile. If not
>> present, glibc will skip the generation which isn't reproducible.
>>
>> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
>> ---
>> meta/recipes-core/glibc/glibc.inc | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-core/glibc/glibc.inc b/meta/recipes-core/glibc/glibc.inc
>> index 252fd56c13c..f1a6ae2a245 100644
>> --- a/meta/recipes-core/glibc/glibc.inc
>> +++ b/meta/recipes-core/glibc/glibc.inc
>> @@ -6,7 +6,7 @@ DEPENDS = "virtual/${TARGET_PREFIX}gcc libgcc-initial linux-libc-headers"
>>
>> PROVIDES = "virtual/libc"
>> PROVIDES += "virtual/libintl virtual/libiconv"
>> -inherit autotools texinfo distro_features_check systemd
>> +inherit autotools texinfo distro_features_check systemd gettext
FYI: I forgot to send this one in-reply-to a previous patch. There is
more history here:
http://lists.openembedded.org/pipermail/openembedded-core/2019-June/284158.html
> I suspect this may not do what you expect.
>
> At least as I read the class and recipes, glibc sets
> INHIBIT_DEFAULT_DEPS which means no gettext-native dependency is added,
> instead, configure has --disable-nls added.
Ah, yes I see that also.
>
> Is that what we want?
I guess I'm not sure exactly what we want; It was a while ago so I don't
remember exactly what glibc was doing, but it looks like it was
sometimes generating locales (e.g. the first time it built) and
sometimes not (when rebuilding) depending on the presence of gettext.
>
> I'm curious to understand how glibc locales are ever generated
> correctly and what we're aiming to add here (a gettext-native
> dependency?)
I'm not sure how it ever works correctly :). Perhaps it would be best to
just drop this patch for now until we take a more serious look at
reproducible in the presence of partial recipe rebuilds. I'd rather
focus on getting the existing QA test running ATM.
>
> FWIW gettext-native is a very heavy thing to add in as a dependency
> from a build time perspective.
Yes, that was discussed which is what led to using gettext.bbclass that
might use gettext-minimal-native, but as you pointed out this isn't
whats happening.
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2019-08-28 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 12:45 [PATCH] glibc: Fix locale DEPENDS Joshua Watt
2019-08-28 16:09 ` Richard Purdie
2019-08-28 16:27 ` Joshua Watt [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-27 13:54 Joshua Watt
2019-06-27 16:19 ` Burton, Ross
2019-06-28 13:58 ` Joshua Watt
2019-06-27 19:47 ` Andre McCurdy
2019-06-27 20:15 ` Joshua Watt
2019-06-28 16:37 ` Khem Raj
2019-07-01 23:13 ` Peter Kjellerstedt
2019-07-02 3:25 ` Khem Raj
2019-08-27 12:50 ` Joshua Watt
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=8cd4e5be-e226-a297-daca-1cce33f5af31@gmail.com \
--to=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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