Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 935898 - sys-libs/glibc-2.39-r6: 829MB /usr/lib64/libc.a on catbus.sparc
Summary: sys-libs/glibc-2.39-r6: 829MB /usr/lib64/libc.a on catbus.sparc
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: Sparc Linux
: Normal normal
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 933986
  Show dependency tree
 
Reported: 2024-07-12 13:50 UTC by Arthur Zamarin
Modified: 2024-07-20 19:35 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2024-07-12 13:50:04 UTC
From random looking at what takes space on "/" filesystem of catbus.sparc devbox, I noticed this:

> # du -sh /usr/lib64/libc.a 
> 829M    /usr/lib64/libc.a

Meanwhile on my amd64 PC, it is just 23MB. It would be interesting to know (and maybe report upstream?) why such a big difference.
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-07-20 01:22:18 UTC
I actually saw this on amd64 earlier with:

before: 360M libc.a
after `strip`: 3.7M libc.a

I wonder if we're not stripping static libraries correctly in Portage (might only show up with splitdebug or something).

For kicks, I stripped the libc.a on catbus and got:
catbus /etc/portage # ls -hal /usr/lib64/libc.a
-rw-r--r-- 1 root root 829M Jun 19 16:51 /usr/lib64/libc.a
catbus /etc/portage # strip /usr/lib64/libc.a
catbus /etc/portage # ls -hal /usr/lib64/libc.a
-rw-r--r-- 1 root root 3.2M Jul 19 18:19 /usr/lib64/libc.a

which makes me think something is off.
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-07-20 01:23:46 UTC
I saw https://lore.kernel.org/all/1721415498-29682-1-git-send-email-mark.hatle@kernel.crashing.org/ by chance earlier, might be interesting to compare their implementation in openembedded...