From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] build failure mbstate_t not declared
Date: Fri, 11 Jul 2008 06:55:44 +0200 [thread overview]
Message-ID: <4876E7D0.3010305@atmel.com> (raw)
In-Reply-To: <4876DA46.6040601@acsatlanta.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joseph G. Boike skrev:
| Ulf Samuelsson wrote:
| Joseph G. Boike skrev:
| | Hi,
| | I checked out the latest buildroot and tried to build it but keep
| | getting errors regarding mbstate_t not being declared.
| | Here's a section of the output (there are many more lines with the same
| | error, but I wanted to keep the post short.)
| | Any suggestions?
|
| Try building an existing board which is known to work.
|
| $ make at91sam9260dfc_defconfig
| $ make
|
| BR
| Ulf Samuelsson.
|
| Did make at91sam9260dfc_defconfig w/ the default setting everywhere
| except I chose 2.6.26 kernel and I still see the same results.
google -> mbstate_t is defined in wchar.h which gets included
if you enable WCHAR.
You are sure you did not disable this in buildroot?
BR
Ulf Samuelsson
| Regards,
| Joe
| _______________________________________________
| buildroot mailing list
| buildroot at uclibc.org
| http://busybox.net/mailman/listinfo/buildroot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIdufQAyRRH5cXxqwRAiBFAJ9ZSQTw29WCBi2KM924Rhgrim/z/wCggG7r
gA9MQ4KOcQ+xBN543QlrpK4=
=yre7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-07-11 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 18:49 [Buildroot] build failure mbstate_t not declared Joseph G. Boike
2008-07-10 21:35 ` Ulf Samuelsson
2008-07-11 3:57 ` Joseph G. Boike
2008-07-11 4:55 ` Ulf Samuelsson [this message]
2008-07-11 11:49 ` Joseph G. Boike
2008-07-11 19:53 ` Joseph G. Boike
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=4876E7D0.3010305@atmel.com \
--to=ulf.samuelsson@atmel.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.