Bug 545630 – Emerging sys-devel/llvm-3.6.0 with debugging symbols needs more than 26 GiB of space in PORTAGE_TMPDIR

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Nico R. 2015-04-05 16:00:20 UTC]

Created attachment 400612 [details]
Sizes of files within the $PORTAGE_TMPDIR/portage/sys-devel/llvm-3.6.0/work/ hierarchy.

I was unable to emerge sys-devel/llvm-3.6.0 on a box where PORTAGE_TMPDIR is 26 GiB large. It stopped during the install phase with “No space left on device”.


I’m attaching several log files. For some reason, the ‘emerge --info’ does not show that it’s a multilib build (‘abi_x86_32’ is set via package.use), but it is (see emerge log file).

work-size.log is the output of
# du -BK /var/tmp/portage/sys-devel/llvm-3.6.0/work

[Comment 1 Nico R. 2015-04-05 16:01:25 UTC]

Created attachment 400614 [details]
output of ‘emerge --info =sys-devel/llvm-3.6.0’

[Comment 2 Nico R. 2015-04-05 16:02:55 UTC]

Created attachment 400616 [details]
compressed emerge log file

[Comment 3 Nico R. 2015-04-05 16:07:25 UTC]

Addendum to comment 0 and attachment 400612 [details]: yes, my $PORTAGE_TMPDIR was almost empty when I tried to emerge the package. As is visible from work-size.log, the work/ hierarchy was almost 18.5 GiB in total.

[Comment 4 Nico R. 2015-04-05 16:09:38 UTC]

I believe that this bug may be related to bug 417307. But, then again, I may be totally wrong…

[Comment 5 Bernard Cafarelli 2015-04-16 11:54:57 UTC]

Thanks for the report! In fact this is kind of a duplicate/follow-up of #479356

There is some code to warn against the heavy disk usage in debug, but it does not trigger in your case (it checks USE=debug, -g and -gdb CFLAGS, not -ggdb2)

I updated the ebuild to check is-flagq '-g?(gdb)?([1-9])' (already in use in chromium and qt eclasses).