On Saturday 09 September 2006 21:43 Julien TOUCHE wrote: > $ set | egrep "^LC_" nothing? > $ echo $LANG nothing? > $ locale > bash: locale: command not found isn't here?
> > What happens if you lie to fsvs and try a utf8-locale? > > $ locale -a | grep utf8 > > should show you some, and then > > $ LC_ALL=<the locale you try> make run-tests > $ echo $LC_ALL > $ LC_ALL= gmake run-tests ... > An error occurred at 21:35:02.933: Invalid argument (22) > in hlp___get_conv_handle: Conversion from 646 to UTF-8 is not supported ... > $ LC_ALL=C gmake run-tests ... > An error occurred at 21:35:31.906: Invalid argument (22) > in hlp___get_conv_handle: Conversion from 646 to UTF-8 is not supported ... > $ LC_ALL=en gmake run-tests ... > An error occurred at 21:36:58.695: Invalid argument (22) > in hlp___get_conv_handle: Conversion from 646 to UTF-8 is not supported ... > $ LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 gmake run-tests ... > An error occurred at 21:41:31.334: Invalid argument (22) > in hlp___get_conv_handle: Conversion from 646 to UTF-8 is not supported ... > also fsvs -d st returned: > 19:14:46.172 main[fsvs.c:443] LC_ALL gives C > 19:14:46.174 main[fsvs.c:450] LC_CTYPE gives C > 19:14:46.174 main[fsvs.c:461] codeset found to be 646 I now found two posts http://gcc.gnu.org/ml/java-patches/2002-q1/msg00944.html and http://archives.postgresql.org/pgsql-hackers/2003-05/msg00744.php; according to them you could try with LC_CTYPE=8859_1 or LC_CTYPE=ASCII. > maybe if somes functions you use are dependent on configure/compile > options of libiconv ? I don't know, I thought that these were standard UNIX functions with some default behaviour? Regards, Phil -- Versioning your /etc, /home or even your whole installation? Try fsvs (fsvs.tigris.org)! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
