From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-13
Date: Mon, 14 Apr 2014 10:58:16 +0200 [thread overview]
Message-ID: <20140414105816.322a1761@skate> (raw)
In-Reply-To: <20140414084230.GD9805@tarshish>
Dear Baruch Siach,
On Mon, 14 Apr 2014 11:42:30 +0300, Baruch Siach wrote:
> > #ifdef __USE_SVID
> > /* Determine whether the string value of RESPONSE matches the affirmation
> > or negative response expression as specified by the LC_MESSAGES category
> > in the program's current locale. Returns 1 if affirmative, 0 if
> > negative, and -1 if not matching. */
> > extern int rpmatch (__const char *__response) __THROW __nonnull ((1)) __wur;
> > #endif
>
> Seems to be a patched uClibc.
Yes, see uclibc-0033-rpmatch-backport-function.patch in Buildroot.
> > See
> > http://free-electrons.com/~thomas/pub/peko-i686-wchar-toolchain.tar.xz
> > for a tarball of the full toolchain. But you will most likely not be
> > able to use it: it's built to run on a PowerPC machine :)
>
> So what is the correct solution for this?
The ideal solution would be to have a configure.ac test for rpmatch,
but unfortunately, mtd-utils do not use autoconf.
I believe we said that we should not include patches that add
functionality to uClibc, but it creates a difference between our
patched uClibc, and other toolchains that don't have the same patches
for uClibc.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-14 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-13 Thomas Petazzoni
2014-04-14 6:51 ` Baruch Siach
2014-04-14 7:15 ` Thomas Petazzoni
2014-04-14 7:58 ` Baruch Siach
2014-04-14 8:30 ` Thomas Petazzoni
2014-04-14 8:42 ` Baruch Siach
2014-04-14 8:58 ` Thomas Petazzoni [this message]
2014-04-14 9:07 ` Baruch Siach
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=20140414105816.322a1761@skate \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.