From: Jonas de Buhr <jonas.de.buhr@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Kernel compiles ... monitoring
Date: Mon, 26 Sep 2011 22:47:06 +0200 [thread overview]
Message-ID: <20110926224706.15baecc7@toxic.dbnet> (raw)
In-Reply-To: <loom.20110926T213323-579@post.gmane.org>
hi harry!
don't take my word for it, but i don't think there is an easy solution
to this :)
cmake creates makefiles which show the percentage completed in a build
step. maybe you can look into how it does that and apply that to the
kernel?
/jonas
>Harry <hputnam3 <at> gmail.com> writes:
>
>>
>> How can one tell how far along a kernel compile is? I can see the
>> modules being built in /var/log/genkernel.log
>> (Aside: Please, no hysteria about using genkernel)
>>
>> But I'd like to know of some way to guesstimate how much of the
>> process is completed. Is there a list the compile has generated and
>> is following somewhere under /usr/src/linux? Or some other way of
>> knowing where the compile is in terms of percentage completed?
>
>Just reporting a further bit on this:
>You might think that tailing the log output and grepping for the
>module names in .config would be one way, and I suppose it is, but no
>directly because the compile does not appear to follow .config all the
>time.
>
>Seems to follow closely when there modules in a row, but then jumps to
>whole different sections... so still not very helpful
>
>
>
>
>
next prev parent reply other threads:[~2011-09-26 20:48 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 [this message]
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
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=20110926224706.15baecc7@toxic.dbnet \
--to=jonas.de.buhr@gmx.net \
--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