From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Need iconv(): fatal error: iconv.h: No such file or directory
Date: Tue, 6 Jan 2015 16:46:15 +0100 [thread overview]
Message-ID: <20150106164615.72ed36f0@free-electrons.com> (raw)
In-Reply-To: <a137651a680a46959923e90be1485e87@exch13-mail05.win.slac.stanford.edu>
Dear Williams Jr., Ernest L.,
On Tue, 6 Jan 2015 15:39:47 +0000, Williams Jr., Ernest L. wrote:
> In this case my package/application is external to buildroot.
>
> I have set the following in my ".config" using make xconfig:
> BR2_TOOLCHAIN_BUILDROOT_LOCALE
>
> Like so,
> BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
>
> After typing make, I expect to see "iconv.h" in ${STAGING_DIR}/usr/include
> But it is not, there. :(
>
> Must, I rebuild everything from scratch ?
Yes.
See http://buildroot.org/downloads/manual/manual.html#full-rebuild:
"""
When the toolchain configuration is changed, a complete rebuild
generally is needed. Changing the toolchain configuration often
involves changing the compiler version, the type of C library or its
configuration, or some other fundamental configuration item, and these
changes have an impact on the entire system.
"""
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-06 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 6:17 [Buildroot] Need iconv(): fatal error: iconv.h: No such file or directory Williams
2015-01-06 8:28 ` Thomas Petazzoni
2015-01-06 15:39 ` Williams
2015-01-06 15:46 ` Thomas Petazzoni [this message]
2015-01-06 15:55 ` Williams
2015-01-06 16:05 ` Thomas Petazzoni
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=20150106164615.72ed36f0@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox