public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Kernel compiles ... monitoring
Date: Mon, 26 Sep 2011 19:15:36 -0500	[thread overview]
Message-ID: <CAEH5T2MvH=na1vCuGA=MZF=PweNS8KaxUYgBmwhM44AzcNOvQg@mail.gmail.com> (raw)
In-Reply-To: <87aa9qnbwn.fsf@newsguy.com>

On Mon, Sep 26, 2011 at 6:04 PM, Harry <hputnam3@gmail.com> wrote:
> Sounds like there is no real way unless as you say.  I've been
> wrestling with kernel build after kernel build trying to get a new
> install booted.  Many failures led me to finally resorting to
> genkernel... but you may know already that is a full day of compile at
> least.
>
> But I'm seeing really massive times even on the trimmed down kernels
> where I've set only known things I need.
>
> This is happening in a chroot from sysrescueCD on an older P4 with 2G
> ram.  But my god, I'm seeing hrs and hrs of compile time go by even on
> a lean mean menuconfig produced .config.
>
> Is this pretty normal?

No, I don't think that's normal... for that CPU it should be something
like 10-15 minutes maybe.



      parent reply	other threads:[~2011-09-27  0:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 15:59 [gentoo-user] Kernel compiles ... monitoring Harry
2011-09-26 19:38 ` [gentoo-user] " Harry
2011-09-26 20:47   ` Jonas de Buhr
2011-09-26 21:40 ` [gentoo-user] " Paul Hartman
2011-09-26 23:04   ` [gentoo-user] " Harry
2011-09-27  0:06     ` Brennan Shacklett
2011-09-27  0:08     ` Alan McKinnon
2011-09-27  1:42       ` Harry Putnam
2011-09-27  1:59         ` Michael Mol
2011-09-27  2:01         ` Pandu Poluan
2011-09-27  3:11           ` Paul Hartman
2011-09-27 11:43         ` Jonas de Buhr
2011-09-27  0:14     ` Michael Orlitzky
2011-09-27  0:15     ` Paul Hartman [this message]

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='CAEH5T2MvH=na1vCuGA=MZF=PweNS8KaxUYgBmwhM44AzcNOvQg@mail.gmail.com' \
    --to=paul.hartman+gentoo@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