Bug 621 - BR2_USE_WCHAR does not seem to enable WCHAR support in uClibc
Summary: BR2_USE_WCHAR does not seem to enable WCHAR support in uClibc
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: Other Linux
: P5 enhancement
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-20 17:43 UTC by Seth LaForge
Modified: 2009-09-20 19:25 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build: buildroot-2009.08-2009.09.18


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Seth LaForge 2009-09-20 17:43:31 UTC
I just built withe BR2_USE_WCHAR=y, and that does not seem to enable WCHAR support in uClibc - it looks like the variable just isn't hooked up properly?

I can provide more details if you can't replicate.
Comment 1 Peter Korsgaard 2009-09-20 18:05:20 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)
Comment 2 Seth LaForge 2009-09-20 19:25:12 UTC
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.