Skip to contentSkip to conversation

2.6.13-rc5 randconfig kernel build errors

DISCUSSION Grant Coady 2 participants 4 messages Aug 2, 2005 – Aug 3, 2005

lore
Share & tools
lore
#0 lore raw

Greetings,

Preliminary results, better sample (some hundreds) in a day or so.

2.6.13-rc5
~~~~~~~~~~
Done processing 70 random builds, from which:
### 6 .configs produced errors
### 4 .configs produced undefs
### 29 .configs produced warnings

# zcat result-report-error-abbrev.gz|cut -d: -f2-
arch/i386/mach-es7000/es7000.h:82: error: field `id' has incomplete type
arch/i386/mach-es7000/es7000.h:88: error: field `Header' has incomplete type
arch/i386/mach-es7000/es7000plat.c:154: error: `es7000_rename_gsi' undeclared (first use in this function)
arch/i386/mach-es7000/es7000plat.c:168: warning: implicit declaration of function `acpi_find_rsdp'
arch/i386/mach-es7000/es7000plat.c:170: error: dereferencing pointer to incomplete type
drivers/char/ipmi/ipmi_msghandler.c:1397: warning: `ipmb_file_read_proc' defined but not used
drivers/char/ipmi/ipmi_msghandler.c:1406: warning: `version_file_read_proc' defined but not used
drivers/char/ipmi/ipmi_msghandler.c:1416: warning: `stat_file_read_proc' defined but not used
drivers/mtd/maps/nettel.c:419: error: `ROOT_DEV' undeclared (first use in this function)
drivers/mtd/maps/nettel.c:419: warning: implicit declaration of function `MKDEV'
include/asm-i386/mach-default/mach_apic.h: At top level:
include/asm-i386/mach-default/mach_apic.h:100: error: dereferencing pointer to incomplete type
include/asm-i386/mach-default/mach_apic.h:109: error: `phys_cpu_present_map' undeclared (first use in this function)
include/asm-i386/mach-visws/do_timer.h:32: error: `i8259A_lock' undeclared (first use in this function)
sound/core/memalloc.c:658: error: `snd_mem_proc' undeclared (first use in this function)

Details: http://scatter.mine.nu/test/kernel/2.6.13-rc5/

Grant.

#1 lore raw
Quoted 3 lines · Grant Coady

Greetings,

Preliminary results, better sample (some hundreds) in a day or so.

After 300 random builds, add one more error:
drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this function) drivers/acpi/osl.c:61:10: empty file name in #include

Cheers,
Grant.

#2 lore raw
Quoted 9 lines · Grant Coady
Quoted 3 lines · Grant Coady

Greetings,

Preliminary results, better sample (some hundreds) in a day or so.

After 300 random builds, add one more error:
drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this function) drivers/acpi/osl.c:61:10: empty file name in #include

Please exclude builds with CONFIG_STANDALONE=n.

And please don't send every new error you are finding to this list. As I've already said generating the errors is the the easy part - analyzing them is the real work.

It would be best if you would do this yourself and send specific bug reports (or even patches) for the problems you've find.

If you want to publish the errors you've found, send a pointer to a location where it is available _once_ and update the information there.

This is e.g. how Jan Dittmer is doing it with his very valuable cross compile site [1] - he doesn't send daily emails but if I want to know the information I can always find it there.

Quoted 2 lines

Cheers,
Grant.

cu
Adrian

[1] http://l4x.org/k/

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#3 lore raw

Hi Adrian,

Quoted 6 lines · Adrian Bunk
Quoted 4 lines

After 300 random builds, add one more error:
drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this function) drivers/acpi/osl.c:61:10: empty file name in #include

Please exclude builds with CONFIG_STANDALONE=n.

Okay.

Quoted 2 lines

And please don't send every new error you are finding to this list.

Go tell the dimwits not trimming their posts to control themselves, I'm generating minimal traffic with this project. Certainly far less traffic then that imbecile arguing for _his_ default setting.

Quoted 2 lines

As I've already said generating the errors is the the easy part - analyzing them is the real work.

Starting somewhere, I'll settle :) It is this feedback I need at start -- sorts of things to exclude. I'll not get any feedback without reporting stuff to the list.

Quoted 3 lines

It would be best if you would do this yourself and send specific bug reports (or even patches) for the problems you've find.

I looked at that AmlCode error source file and grepping for a match failed for entire source tree, so did not understand it.

Quoted 3 lines

If you want to publish the errors you've found, send a pointer to a location where it is available _once_ and update the information there.

Killfile me. I'm posting far less noise to lkml per month than your daily line count of repetitive, non-informational space wasting dot_sig.

Thanks,
Grant.