1 |
On Wed, Jul 23, 2008 at 10:04 AM, Nikos Chantziaras <realnc@×××××.de> wrote: |
2 |
> Kevin O'Gorman wrote: |
3 |
>> |
4 |
>> I run gentoo x86 stable, so that I usually avoid this sort of thing. |
5 |
>> |
6 |
>> This kernel, however, looks balky to me, because it's reporting |
7 |
>> warnings and other oddities during compilation. I don't like warnings |
8 |
>> at any time, and with the kernel's make wrappers cleaning up the |
9 |
>> output they tend to stand out. |
10 |
>> |
11 |
>> Here's what I get: |
12 |
>> -- various type/attribute warnings |
13 |
>> -- reports of deprecated elements |
14 |
>> -- a report of "section mismatches", and instructions to use "make |
15 |
>> CONFIG_DEBUG_SECTION_MISMATCH=y" to find details. |
16 |
>> |
17 |
>> All that being said, the compilation completes, and I can boot it. I |
18 |
>> don't know the cause, but I have been unable to get vmware-server |
19 |
>> running on it, and I'm going back to the previous kernel for that |
20 |
>> reason. |
21 |
> |
22 |
> I hope you're not implying that a kernel should not be declared stable |
23 |
> simply because a vmware product lags behind in kernel support? vmware 4 |
24 |
> lacks support for kernel 2.6 alltogether, maybe we should only have 2.4 |
25 |
> stable because of that. |
26 |
|
27 |
I am not suggesting that the vmware stuff should prevent releasing a |
28 |
kernel. I am suggesting that pages of |
29 |
cryptic and unusual output, not to mention warnings and deprecation |
30 |
from the kernel's own make is cause for users to worry about the |
31 |
kernel and wonder WTF. |
32 |
|
33 |
++ kevin |
34 |
|
35 |
-- |
36 |
Kevin O'Gorman, PhD |