Bug 54508 – Huge size of /usr/lib/gconv on amd64 (sys-libs/glibc-2.3.4.20040605)

• Product: Gentoo Linux
• Status: RESOLVED WORKSFORME

[Description Evgeny Stambulchik 2004-06-20 04:19:34 UTC]

On amd64, glibc iconv modules take a lot of disk space. Compare with x86:
# du -s /usr/lib/gconv             
197968  /usr/lib/gconv
# du -s /emul/linux/x86/usr/lib/gconv/
3964    /emul/linux/x86/usr/lib/gconv/

# ls -l /usr/lib/gconv/ISO8859-1.so
-rwxr-xr-x  1 root root 1054928 Jun 20 11:27 /usr/lib/gconv/ISO8859-1.so
# ls -l /emul/linux/x86/usr/lib/gconv/ISO8859-1.so
-rwxr-xr-x  1 root root 5872 Feb 12 09:34 /emul/linux/x86/usr/lib/gconv/ISO8859-1.so

Why is this?


Reproducible: Always
Steps to Reproduce:

[Comment 1 Evgeny Stambulchik 2004-06-20 06:13:17 UTC]

Probably it's not amd64-specific, since in the previous version of glibc (glibc-2.3.3_pre20040529) on amd64 the size of the gconv dir is small as well (~ 5 MB).

[Comment 2 Travis Tilley (RETIRED) 2004-06-27 14:42:31 UTC]

hmm...
28M     /usr/lib/gconv/

ayanami net-p2p # strip --strip-unneeded /usr/lib/gconv/*
strip: /usr/lib/gconv/gconv-modules: File format not recognized
strip: /usr/lib/gconv/gconv-modules.cache: File format not recognized
ayanami net-p2p # du -ch /usr/lib/gconv/
5.8M    /usr/lib/gconv/

you wouldnt happen to be using FEATURES="nostrip" USE="debug", would you?

[Comment 3 Evgeny Stambulchik 2004-06-27 23:31:10 UTC]

> you wouldnt happen to be using FEATURES="nostrip" USE="debug", would you?

Nope.

# file ISO8859-1.so 
ISO8859-1.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), stripped

But here comes an interesting thing:
# ls -l ISO8859-1.so
-rwxr-xr-x  1 root root 1054928 Jun 20 18:44 ISO8859-1.so*
# du -s ISO8859-1.so
1036    ISO8859-1.so
# strip --strip-unneeded ISO8859-1.so
# ls -l ISO8859-1.so
-rwxr-xr-x  1 root root 1054928 Jun 28 09:24 ISO8859-1.so*
# du -s ISO8859-1.so
11      ISO8859-1.so

Apparently, these files are sparse. I wonder why??

[Comment 4 Danny van Dyk (RETIRED) 2004-08-19 14:59:01 UTC]

Can't reproduce this. If this bug start making trouble then reopen this bug please

Resolved as WORKSFORME