From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Make sure WCHAR is enabled if native binutils will be build
Date: Tue, 19 Aug 2014 02:03:25 +0400 [thread overview]
Message-ID: <1408399407-23604-1-git-send-email-abrodkin@synopsys.com> (raw)
binutils starting at least from 2.23 when build for target require uClibc
configured with UCLIBC_HAS_WCHAR otherwise:
==========
libtool: link: [...] -o as-new [...]
read.o: In function `read_symbol_name':
read.c:(.text+0x3634): undefined reference to `mbstowcs'
collect2: error: ld returned 1 exit status
==========
because "mbstowcs" won't be compiled in.
That's why we need to make sure WCHAR is enabled in toolchain for all
packages that require native binutils.
Alexey Brodkin (2):
binutils: troubleshoot native binutils building (add WCHAR dependency)
packages: add WCHAR dependency for packages that select native
binutils
package/binutils/Config.in | 1 +
package/dropwatch/Config.in | 1 +
package/oprofile/Config.in | 1 +
3 files changed, 3 insertions(+)
--
1.9.3
next reply other threads:[~2014-08-18 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 22:03 Alexey Brodkin [this message]
2014-08-18 22:03 ` [Buildroot] [PATCH 1/2] binutils: troubleshoot native binutils building (add WCHAR dependency) Alexey Brodkin
2014-08-18 22:03 ` [Buildroot] [PATCH 2/2] packages: add WCHAR dependency for packages that select native binutils Alexey Brodkin
2014-09-23 11:05 ` [Buildroot] [PATCH 0/2] Make sure WCHAR is enabled if native binutils will be build Alexey Brodkin
2014-09-23 11:22 ` Thomas Petazzoni
2014-09-23 11:31 ` Alexey Brodkin
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=1408399407-23604-1-git-send-email-abrodkin@synopsys.com \
--to=alexey.brodkin@synopsys.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