From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: crossgcc@sourceware.org
Subject: Re: Trouble with Locale
Date: Wed, 17 Aug 2016 20:20:00 -0000 [thread overview]
Message-ID: <CAK7rcp_ubA6fYb+24PLKmringThV1jS2ygAsO2zTecUVFH060Q@mail.gmail.com> (raw)
In-Reply-To: <20160817193901.GJ22524@waldemar-brodkorb.de>
Well, I did need to be able to use whichever toolchain was specified
to build rust. I suppose there is a dedicated directory for the
particular buildroot internal toolchain. I will try and point the rust
compilation toward that in order to maintain a common version of
underlying dependencies between software.
Does this sound like a correct approach?
On Wed, Aug 17, 2016 at 3:39 PM, Waldemar Brodkorb <wbx@openadk.org> wrote:
> Hi,
> Kenneth Adam Miller wrote,
>
>> I'm adding a uclibc cross compile target for the rust compiler. I am using the
>> 1.0.9 version, the most up to date that cross tool allows. It isn't so much
>> embedded device support that is desired as it is that we want to reduce our
>> trusted computing base as much as possible. Musl was another possibility, but I
>> haven't had time to explore that route.
>>
>> Can a uclibc cross compiler be compiled with locale support at all?
>
> Yes. Can you cross-check with internal toolchain support in Buildroot?
> They use the latest uClibc-ng version and I remember to have fixed
> an Locale problem in the past for some Host systems.
>
> best regards
> Waldemar
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2016-08-17 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 0:57 Kenneth Adam Miller
2016-08-17 3:45 ` Kenneth Adam Miller
2016-08-17 4:09 ` Kenneth Adam Miller
2016-08-17 5:48 ` Waldemar Brodkorb
[not found] ` <CAK7rcp-XuU26jx1aSkKjXP88gEGy5E2K0XG=ZxzBT79rK9WwLQ@mail.gmail.com>
2016-08-17 14:29 ` Kenneth Adam Miller
2016-08-17 19:39 ` Waldemar Brodkorb
2016-08-17 20:20 ` Kenneth Adam Miller [this message]
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=CAK7rcp_ubA6fYb+24PLKmringThV1jS2ygAsO2zTecUVFH060Q@mail.gmail.com \
--to=kennethadammiller@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=wbx@openadk.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).