From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist-2018.06.0: host-localedef incompatible with OSELAS-Toolchain 2016.06.1
Date: Fri, 22 Jun 2018 09:01:37 +0200 [thread overview]
Message-ID: <20180622070137.k7i4why2u5pljzkl@pengutronix.de> (raw)
In-Reply-To: <6d672b047d70110e5fe86b4e7fa1d88379686a17.camel@allegion.com>
On Tue, Jun 19, 2018 at 03:08:42PM +0000, Baeuerle, Florian wrote:
> I'm having troubles building a ptxdist Project with ptxdist-2018.06.0 in
> combination with the OSELAS-Toolchain 2016.06.1.
>
> The new hostdef-locale's localedef cannot handle the locales from the
> old OSELAS-Toolchain:
>
> generating "en_US.UTF-8" - this can take some time
> calling localedef binary failed
> /usr/local/lib/ptxdist-2018.06.0/rules/locales.make:28: recipe for target '/build/platform-core-am335x/state/locales.install' failed
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_CTYPE'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_NUMERIC'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_TIME'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_COLLATE'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_MONETARY'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_MESSAGES'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_PAPER'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_NAME'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_ADDRESS'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_TELEPHONE'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_MEASUREMENT'
> [error] LC_IDENTIFICATION: unknown standard `en_US:2000' for category `LC_IDENTIFICATION'
> [error] no output file produced because errors were issued
> make: *** [/build/platform-core-am335x/state/locales.install] Error 1
>
>
> This is caused by 47116f66f411d4dadfce42c2fdd6d41b351ccfd4.
>
> That change probably pulled in this change:
>
> https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=900f59f084bfe35cb389bbe0dc464413a1a38e90
Indeed. I think adding "i18n:2000" to the list of standards introduced in
this commit should help. Can you try that and send a patch if it works?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-06-22 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 15:08 Baeuerle, Florian
2018-06-22 7:01 ` Michael Olbrich [this message]
2018-06-22 14:15 ` Ladislav Michl
2018-06-22 15:17 ` Ladislav Michl
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=20180622070137.k7i4why2u5pljzkl@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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