From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] local autobuild failures
Date: Sat, 18 Jul 2020 14:10:49 +0200 [thread overview]
Message-ID: <20200718141049.115c1bb0@windsurf.home> (raw)
In-Reply-To: <CAEyMn7YeeODW9bKxQYY1oXotvyNG+QX41kbGhmrHKiqOsd0hdQ@mail.gmail.com>
On Sat, 18 Jul 2020 08:14:39 +0200
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> uclibc:
> https://pastebin.com/D459072K
> https://filebin.net/ciweyuk38es1igea
This one is I believe a build environment issue indeed: you need one
UTF-8 locale available in your system. However, this is normally
checked by the following bits of code in
support/dependencies/dependencies.sh:
if grep ^BR2_NEEDS_HOST_UTF8_LOCALE=y $BR2_CONFIG > /dev/null; then
if ! which locale > /dev/null ; then
echo
echo "You need locale support on your build machine to build a toolchain supporting locales"
exit 1 ;
fi
if ! locale -a | grep -q -i -E 'utf-?8$' ; then
echo
echo "You need at least one UTF8 locale to build a toolchain supporting locales"
exit 1 ;
fi
fi
Could you have a look at whether you have an UTF-8 locale or not ?
> haproxy:
> https://pastebin.com/YxSv6FSJ
> https://filebin.net/pydnt9vdhfkzn53n
This is not a build environment issue. Either it is fixed by commit
37eda7196e3414fbd3a054b7b43980d2219faffb, or it is another related
issue, but clearly not related to your build environment.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-18 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 6:14 [Buildroot] local autobuild failures Heiko Thiery
2020-07-18 12:10 ` Thomas Petazzoni [this message]
2020-07-18 18:10 ` Heiko Thiery
2020-07-19 8:03 ` Thomas Petazzoni
2020-07-19 18:12 ` Heiko Thiery
2020-07-19 19:44 ` Yann E. MORIN
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=20200718141049.115c1bb0@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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