disableing locale completely.

[seema ravandale]

Hi.

I am working on toolchain maintained for arm port. I am using option
disable-nls to disable language internationalization. so default locales
installed  will be "C" and "POSIX". To set up other locale, i use
localedef option.

As far my knowledge, disable-nls will disable functionality of gettext
utility.
With the libc installation, locale data too get installed, By locale
data, i meant local definitions file, charmaps and message formatter
file (.mo files).

On disabling language internationalization, why are the locale data
files still needed?
Is there a way, or any option already available in libc not to get
locale data files installed?

Thanking you.

-Seema Ravandale
software Engg,
Azingo soft system pvt ltd,
Pune, India.

[Carlos O'Donell-3]

seema ravandale wrote:
> I am working on toolchain maintained for arm port. I am using option
> disable-nls to disable language internationalization. so default locales
> installed  will be "C" and "POSIX". To set up other locale, i use
> localedef option.
>
> As far my knowledge, disable-nls will disable functionality of gettext
> utility.

Yes, I believe that's the case.

> With the libc installation, locale data too get installed, By locale
> data, i meant local definitions file, charmaps and message formatter
> file (.mo files).
>
> On disabling language internationalization, why are the locale data
> files still needed?

Probably because nobody tries it out. You can always remove the files by
hand.

> Is there a way, or any option already available in libc not to get
> locale data files installed?
>
> Thanking you.

Alternatively you may wish to look at http://www.eglibc.org, which is
libc but with configuration options. Take a look at the
OPTIONS_EGLIBC_LOCALES feature which disables locale definitions.

Cheers,
Carlos.
--
Carlos O'Donell
CodeSourcery
carlos@...
[phone] x716

[Pramod KB]

You can use localedef command to install preferred locales needed by you instead of  installing every locale available in  the glibc/localedata/loacle_available_file.

More info about the command is available in glibc source INSTALL.

Pramod KB.

seema ravandale wrote:

Hi.

I am working on toolchain maintained for arm port. I am using option
disable-nls to disable language internationalization. so default locales
installed  will be "C" and "POSIX". To set up other locale, i use
localedef option.

As far my knowledge, disable-nls will disable functionality of gettext
utility.
With the libc installation, locale data too get installed, By locale
data, i meant local definitions file, charmaps and message formatter
file (.mo files).

On disabling language internationalization, why are the locale data
files still needed?
Is there a way, or any option already available in libc not to get
locale data files installed?

Thanking you.

-Seema Ravandale
software Engg,
Azingo soft system pvt ltd,
Pune, India.

[Kaz Kylheku-3]

seema ravandale <seema.ravandale@...> wrote:
> Is there a way, or any option already available in libc not to get
> locale data files installed?

Hi Seema,

Don't you build glibc into a separate installation directory and then
copy from there into your toolchain's sysroot?

In that step, you can strip out whatever you don't want.

Why would you care about the locale stuff being in the toolchain
anyway? Disk space on development workstations is cheap. Where
space may still be premium, though, is on a small, embedded Linux
system which only have flash storage.

In that case, you may want to scrub unwanted stuff like localization
from /all/ of the packages, not just glibc.

In the cross-compiled Linux distro that I maintain, this is handled
by the packaging scripts. The binary packages themselves are
built completely, with all of their locale support, so that we have
the choice of including that if we want.  Besides, it's too much of
a chore for each package to figure out exactly how to configure it not
to build or install locale materials (if it can be done at all),
and then patch it if it doing so breaks its build, haha.

It's our scripts which put a filesystem together, will scrub the
locale information out as they process each tarball. We gave
the task of developing this to a  co-op student who dug up
a locale-cleaning script (from Debian, I think) which he used
as a subroutine.

Google for "localepurge"