From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtomcrypt: fix build without wchar
Date: Sun, 22 Oct 2017 14:37:08 +0200 [thread overview]
Message-ID: <20171022143708.456a666d@windsurf> (raw)
In-Reply-To: <217c4b97cdb72c68b7d6d669b1c3cbb9b47bf4ad.1508242375.git.baruch@tkos.co.il>
Hello,
On Tue, 17 Oct 2017 15:12:55 +0300, Baruch Siach wrote:
> GCC defines wchar_t even when wchar support is disabled in uClibc. The
> LTC_NO_WCHAR macro triggers a local definition of wchar_t that conflicts
> with the GCC defined one. Remove LTC_NO_WCHAR to avoid that.
>
> Fixes:
> http://autobuild.buildroot.net/results/895/895452ac973cab0e0bc22636d39cbec7fbf598d3/
> http://autobuild.buildroot.net/results/c82/c82d0173878e58f7192d3cec271b45763e6ea269/
> http://autobuild.buildroot.net/results/83f/83f433bcb608b341fca2180afa57fc81495bc3b4/
>
> Cc: Francois Perrad <francois.perrad@gadz.org>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/libtomcrypt/libtomcrypt.mk | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Applied to master after updating the autobuilder reference to a result
that we still have in the database, and adding a reference to the
interesting Github discussion.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-22 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 12:12 [Buildroot] [PATCH] libtomcrypt: fix build without wchar Baruch Siach
2017-10-18 14:59 ` François Perrad
2017-10-22 12:37 ` Thomas Petazzoni [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=20171022143708.456a666d@windsurf \
--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.