[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

benh kernel build error



Hi all

I'm trying to build my own 2.4.21-ben2 kernel, and it seems I've messed up
my kernel .config file that I edited for the build. The file is here:

http://www.geocities.com/wolfgangpfeiffer/config.txt

The kernel builds without any error AFAICS if I don't change the default
.config file as shipped with the kernel. That's why I think I made at
least one mistake in my edited version of the .config file.

This is what I have done to build it:

make-kpkg --revision wolfp.1 kernel-image

I also tried
make-kpkg --revision 1.00.wolfp kernel_image
(underscore instead of hyphen) and other versions of the command: to no
avail so far ..

And after the first build failed I entered a
make-kpkg clean
for the following one.

This is the rest of what I could paste from the screen after the last
failed build:

------------------------------------------------------

amd76x_pm.c:141: initializer element is not constant
amd76x_pm.c:141: (near initialization for `amd_nb_driver')
amd76x_pm.c:141: initializer element is not constant
amd76x_pm.c:141: (near initialization for `amd_nb_driver')
amd76x_pm.c:145: `amd_sb_tbl' undeclared here (not in a function)
amd76x_pm.c:145: initializer element is not constant
amd76x_pm.c:145: (near initialization for `amd_sb_driver.id_table')
amd76x_pm.c:147: initializer element is not constant
amd76x_pm.c:147: (near initialization for `amd_sb_driver.remove')
amd76x_pm.c:148: initializer element is not constant
amd76x_pm.c:148: (near initialization for `amd_sb_driver')
amd76x_pm.c:148: initializer element is not constant
amd76x_pm.c:148: (near initialization for `amd_sb_driver')
amd76x_pm.c:152: parse error before `amd_nb_init'
amd76x_pm.c:153: warning: return-type defaults to `int'
amd76x_pm.c:163: parse error before `amd_nb_remove'
amd76x_pm.c:164: warning: return-type defaults to `int'
amd76x_pm.c:164: conflicting types for `amd_nb_remove'
amd76x_pm.c:96: previous declaration of `amd_nb_remove'
amd76x_pm.c: In function `amd_nb_remove':
amd76x_pm.c:165: warning: control reaches end of non-void function
amd76x_pm.c: At top level:
amd76x_pm.c:169: parse error before `amd_sb_init'
amd76x_pm.c:170: warning: return-type defaults to `int'
amd76x_pm.c:180: parse error before `amd_sb_remove'
amd76x_pm.c:181: warning: return-type defaults to `int'
amd76x_pm.c:181: conflicting types for `amd_sb_remove'
amd76x_pm.c:99: previous declaration of `amd_sb_remove'
amd76x_pm.c: In function `amd_sb_remove':
amd76x_pm.c:182: warning: control reaches end of non-void function
amd76x_pm.c: At top level:
amd76x_pm.c:644: parse error before `amd76x_pm_init'
amd76x_pm.c:645: warning: return-type defaults to `int'
amd76x_pm.c:652: parse error before `amd76x_pm_cleanup'
amd76x_pm.c:653: warning: return-type defaults to `int'
amd76x_pm.c: In function `amd76x_pm_cleanup':
amd76x_pm.c:683: warning: control reaches end of non-void function
amd76x_pm.c: At top level:
amd76x_pm.c:687: warning: type defaults to `int' in declaration of
`module_init'
amd76x_pm.c:687: warning: parameter names (without types) in function
declaration
amd76x_pm.c:687: warning: data definition has no type or storage class
amd76x_pm.c:688: warning: type defaults to `int' in declaration of
`module_exit'
amd76x_pm.c:688: warning: parameter names (without types) in function
declaration
amd76x_pm.c:688: warning: data definition has no type or storage class
amd76x_pm.c:482: warning: `activate_amd76x_SLP' defined but not used
make[3]: *** [amd76x_pm.o] Error 1
make[3]: Leaving directory `/usr/src/benh.kernel/drivers/char'
make[2]: *** [_modsubdir_char] Error 2
make[2]: Leaving directory `/usr/src/benh.kernel/drivers'
make[1]: *** [_mod_drivers] Error 2
make[1]: Leaving directory `/usr/src/benh.kernel'
make: *** [stamp-build] Error 2
-----------------------------------------------------------

It seems the error is related to /drivers/char/amd76x_pm.c in the sources,
but I didn't find a hint to the kernel .config option this file is
related to ...

I'm happy even with a hint where the mistake *could* be.

Thanks in anticipation
Wolfgang

-- 
Profile, Links:
http://profiles.yahoo.com/wolfgangpfeiffer




Reply to: