Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)
Junichi Uekawa writes: To ensure some locales are available, I think you can use LOCPATH, and create locales locally, so that the following are available: de_DE ISO-8859-1 en_US ISO-8859-1 fr_FR ISO-8859-1 see /usr/sbin/locale-gen on how to generate these locale data. ok, it's no problem to generate the data, but I cannot find any reference to LOCPATH. Any hints? I couldn't find any reference to LOCPATH either, but setlocale seems to look at directories specified by LOCPATH in addition to (or instead of) the standard location (/usr/lib/locale) ok, next question is how to write the new definitions to the new LOCPATH. the outputdir in localedef seems to be hardcoded. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)
I couldn't find any reference to LOCPATH either, but setlocale seems to look at directories specified by LOCPATH in addition to (or instead of) the standard location (/usr/lib/locale) ok, next question is how to write the new definitions to the new LOCPATH. the outputdir in localedef seems to be hardcoded. The manual page documents: I18NPATH In boot-floppies build-process, itseems to be: mkdir -p $T/usr/lib/locale localedef -i utilities/bogl/C-at-utf-8.in -f UTF-8 \ $T/usr/lib/locale/C@utf-8 so full-path to output file is the final command-line argument to localedef. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)
To ensure some locales are available, I think you can use LOCPATH, and create locales locally, so that the following are available: de_DE ISO-8859-1 en_US ISO-8859-1 fr_FR ISO-8859-1 see /usr/sbin/locale-gen on how to generate these locale data. ok, it's no problem to generate the data, but I cannot find any reference to LOCPATH. Any hints? I couldn't find any reference to LOCPATH either, but setlocale seems to look at directories specified by LOCPATH in addition to (or instead of) the standard location (/usr/lib/locale) One example execution of LOCPATH=/tmp strace locale gives me: . . open(/usr/lib/locale/ja.eucJP/LC_IDENTIFICATION, O_RDONLY) = -1 ENOENT (No such file or directory) open(/tmp/ja.eucjp/LC_IDENTIFICATION, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib/locale/ja.eucjp/LC_IDENTIFICATION, O_RDONLY) = -1 ENOENT (No such file or directory) open(/tmp/ja/LC_IDENTIFICATION, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib/locale/ja/LC_IDENTIFICATION, O_RDONLY) = -1 ENOENT (No such file or directory) . . I also found out that it is mostly undocumented, but apparently is a standard feature pretty much known by those who do know, so documentation is probably very lacking. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
