| 1 |
On Wed, Jul 23, 2008 at 5:06 PM, Volker Armin Hemmann |
| 2 |
<volker.armin.hemmann@××××××××××××.de> wrote: |
| 3 |
> On Mittwoch, 23. Juli 2008, Kevin O'Gorman wrote: |
| 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 |
> |
| 14 |
> harmless. |
| 15 |
> |
| 16 |
>> -- reports of deprecated elements |
| 17 |
> |
| 18 |
> even more harmless |
| 19 |
> |
| 20 |
>> -- a report of "section mismatches", and instructions to use "make |
| 21 |
>> CONFIG_DEBUG_SECTION_MISMATCH=y" to find details. |
| 22 |
> |
| 23 |
> completly harmless. |
| 24 |
> |
| 25 |
> All three 'problems' can be safely ignored. So do it. |
| 26 |
> |
| 27 |
|
| 28 |
And how would I know they're harmless. No offense, but I don't know |
| 29 |
enough about you to evaluate your skill or knowledge. |
| 30 |
|
| 31 |
I have seen lots of build problems over the decades, but these are new |
| 32 |
to me. What I see is that for some time now, kernel builds have been |
| 33 |
utterly clean, admirably free from the tedious command-line echoes |
| 34 |
that obscure any real information from compiler/linker/whatever build |
| 35 |
tools. Suddenly there are three kinds of reports, most of them a kind |
| 36 |
that I cannot evaluate. There is no sign of the care that I've found |
| 37 |
in other builds, where expected artifacts are announced by the build |
| 38 |
("expect 3 strength/reduce errors here"). The kernel build-toolset |
| 39 |
look like they it would take a major project to comprehend, which I do |
| 40 |
not have time for. |
| 41 |
|
| 42 |
So what's a poor user to do? Believe the first poster responding with |
| 43 |
(apparent) authority? Maybe. I'm just going to stay away for a while |
| 44 |
and see what shakes out. |
| 45 |
|
| 46 |
>> |
| 47 |
>> All that being said, the compilation completes, and I can boot it. I |
| 48 |
>> don't know the cause, but I have been unable to get vmware-server |
| 49 |
>> running on it, and I'm going back to the previous kernel for that |
| 50 |
>> reason. |
| 51 |
> |
| 52 |
> complain to vmware - it's their closed source crap that doesn't work. |
| 53 |
|
| 54 |
I have less clout with vmware than I have with the kernel team, I |
| 55 |
would guess, because I don't pay either one, but at least the kernel |
| 56 |
team are not in business to get money from me. But reasonable |
| 57 |
virtualization is essential to some of my own projects, and I have to |
| 58 |
stick with it. If I have to, I'll learn a different tools set, but |
| 59 |
it's not something I take up lightly. |
| 60 |
|
| 61 |
-- |
| 62 |
Kevin O'Gorman, PhD |
Archives