Re: Failed compile kernel with apci patch applied

[Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]

salut fred..

* Frederic Dernbach <fredatwork-GANU6spQydw@public.gmane.org> [2003-10-27 10:04 +0100]:
> 
> I followed the steps you recommended.
> 
> I restarted the whole process from scratch. I installed the 2.4.22
> baseline kernel source files as well as the 2.4.22 acpi patch
> (acpi-20031002-2.4.22.diff.gz).
> 
> "make bzImage" went fine. "make modules" went fine I presume (I did not
> spot any error in the std output or std error that I kept).
> 
> However "make modules_install" terminated with :
> depmod:*** Unresolved symbols in
> /lib/modules/2.4.22-22-acpi/kernel/crypto/autoload.o
> depmod:		crypto_alg_lookup
> depmod:*** Unresolved symbols in
> /lib/modules/2.4.22-22-acpi/kernel/crypto/proc.o
> depmod:		crypto_alg_sem
> depmod:		crypto_alg_list
> 
> Is there anythting wrong that I dod ? 

i suppose you did not do anything wrong. it looks like some relations in
your .config could not be resolved completely by the scripts. at least,
my builds of 2.4.22 did not show these errors. :)

> Can I continue installing the
> newly compiles kernel ? (I'm a newbee with linux kernel).

yes, usually it poses no problem if some modules unnecessary for your setup
are dysfunctional. but do not expect the crypto-system to work.

> For your information that my .config file include the option
> "Cryptographic API" in the "Cyptographic" options of the kernel config
> menu (I use "make menuconfig"). It is checked. Maybe it has something to
> do with.

looks like that. you can uncheck that option and the unresolved symbols
should disappear after a rebuild.

hth,
 sebastian
-- 
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]