1 |
hi harry! |
2 |
|
3 |
don't take my word for it, but i don't think there is an easy solution |
4 |
to this :) |
5 |
|
6 |
cmake creates makefiles which show the percentage completed in a build |
7 |
step. maybe you can look into how it does that and apply that to the |
8 |
kernel? |
9 |
|
10 |
/jonas |
11 |
|
12 |
>Harry <hputnam3 <at> gmail.com> writes: |
13 |
> |
14 |
>> |
15 |
>> How can one tell how far along a kernel compile is? I can see the |
16 |
>> modules being built in /var/log/genkernel.log |
17 |
>> (Aside: Please, no hysteria about using genkernel) |
18 |
>> |
19 |
>> But I'd like to know of some way to guesstimate how much of the |
20 |
>> process is completed. Is there a list the compile has generated and |
21 |
>> is following somewhere under /usr/src/linux? Or some other way of |
22 |
>> knowing where the compile is in terms of percentage completed? |
23 |
> |
24 |
>Just reporting a further bit on this: |
25 |
>You might think that tailing the log output and grepping for the |
26 |
>module names in .config would be one way, and I suppose it is, but no |
27 |
>directly because the compile does not appear to follow .config all the |
28 |
>time. |
29 |
> |
30 |
>Seems to follow closely when there modules in a row, but then jumps to |
31 |
>whole different sections... so still not very helpful |
32 |
> |
33 |
> |
34 |
> |
35 |
> |
36 |
> |