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
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
Hi,
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.
regards,
junichi
Junichi Uekawa writes:
Hi,
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.
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
For correct libstdc++ testresults, the presence for the following
locales is needed:
de_DE ISO-8859-1
en_US ISO-8859-1
fr_FR ISO-8859-1
How can I make sure, that these locales are installed when building
gcc-3.2, gcc-3.3 and gcc-snapshot packages? (Yes, I can check for
these in the rules
6 matches
Mail list logo