public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Can't emerge glibc as it completely fills /var
Date: Mon, 18 Jul 2005 08:36:32 -0700	[thread overview]
Message-ID: <5bdc1c8b050718083667558c93@mail.gmail.com> (raw)

OK, I'm flummoxed. Have I just gotten lucky all these years? I
attempted to emerge a new glibc this morning and I cannot because it
completely fills my 2.7GB /var partition in the process and I end with
a 'no space on device' message! Obviously the emerge doesn't finish
and I'm left to clean up and ponder the meaning of such things. Prior
to starting the emerge the partition is about 30% full so it appears
that the build takes something like 2GB? Can this really be true?

What can I do to get around this? Should this build really take this
much space or is there possibly a bug here somewhere?

dragonfly ~ # emerge -pv glibc 
These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild     U ] sys-libs/glibc-2.3.5 [2.3.4.20041102-r1] -build -debug
-erandom -hardened (-multilib) +nls +nptl +nptlonly -pic (-selinux)
-userlocales 0 kB

Total size of downloads: 0 kB
dragonfly ~ #

There's probably a config option for where this work is done somewhere
else. What would I change to temporarily move the elsewhere if indeed
there is no bug.

Thanks,
Mark

-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2005-07-18 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 15:36 Mark Knecht [this message]
2005-07-18 16:13 ` [gentoo-user] Can't emerge glibc as it completely fills /var Neil Bothwick
2005-07-18 17:05   ` Mark Knecht
2005-07-18 17:16     ` Zac Medico
2005-07-18 17:23       ` David Busby
2005-07-18 17:53     ` Neil Bothwick
2005-07-18 18:11       ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bdc1c8b050718083667558c93@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox