| Summary: | BR2_USE_WCHAR does not seem to enable WCHAR support in uClibc | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Seth LaForge <sethml> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | buildroot-2009.08-2009.09.18 | ||
|
Description
Seth LaForge
2009-09-20 17:43:31 UTC
Why do you think that it doesn't give you WCHAR support? Please do provide more details. In particular, please show the relevant part of your uclibc config (output/toolchain/uClibc-0.9.30.1/.config. It should contain a UCLIBC_HAS_WCHAR=y line - If not, please provide your buildroot config and explain how you built it. Do notice though that you obviously need to recompile everything when you change BR2_USE_WCHAR, and that it isn't detected automatically (do rm -rf output; make) I had done a "make menuconfig", turned on WCHAR support, done "make clean", then "make", and ended up with a no-wchar build, confirmed by doing "make uclibc-menuconfig" and noting that the WCHAR option was not enabled. Apparently "make clean" wasn't enough to clean things out properly. I don't have a directory "output", but I re-extracted buildroot from the tarball and rebuild with BR2_USE_WCHAR on, and it seems to have worked. Thanks! It would be really nice to have a section in the buildroot documentation describing what you need to do when rebuilding after changing various settings, for example: - After changing a toolchain option. - After changing a uclibc or busybox option. (And when do the uclibc or busybox .configs get clobbered?) - After enabling or disabling a package. |