Le Thu, 24 Mar 2011 05:40:59 +0100 Denys Vlasenko <[email protected]> a écrit:
> On Tue, Mar 22, 2011 at 6:30 PM, Seb <[email protected]> wrote: > > [...] > > Then I've finally disabled the LANG checking > > (CONFIG_FEATURE_CHECK_UNICODE_IN_ENV option), which seems to fix the > > problem for me (but will certainly mess on a non-Unicode system). So, > > the problem appears to be in the way busybox interacts with the LANG > > environment variable. > > Fixed in git: > > http://git.busybox.net/busybox/commit/?id=20704f066250744c0c2b84920c27d0fd0aa9e935 Thanks! Nevertheless, I get new strange issues with this release: - a shell compiled with CONFIG_UNICODE_USING_LOCAL enabled still don't work; when I attempt to enter [é], nothing happens, but if I press [del] after, I'm able to eat two characters of the prompt; - I can call /bin/ash in a bash session and even connect to it with login, but when I attempt to use "su -", I get an "su: applet not found" error. This happens however the unicode routines (bbx or glibc) the shell uses. Except this, CONFIG_FEATURE_CHECK_UNICODE_IN_ENV works well, character-wise. @+ Seb. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
