public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
To: sjb <ottaky-XuTx12Z7TonQT0dZR+AlfA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: compile problem
Date: Mon, 26 May 2003 18:13:27 +0200	[thread overview]
Message-ID: <20030526181327.21984b10.nils@kernelconcepts.de> (raw)
In-Reply-To: <3ED1E212.30108-XuTx12Z7TonQT0dZR+AlfA@public.gmane.org>

On Mon, 26 May 2003 09:44:50 +0000
sjb <ottaky-XuTx12Z7TonQT0dZR+AlfA@public.gmane.org> wrote:
> Apologies for this not being a strictly ACPI problem.

It looks so, yes.

> I'm trying to compile an ACPI enabled kernel for my Vaio. I've tried 
> numerous combinations of kernel sources and patches as per the
> pointers from members of this list.
> 
> However, I always get this error during "make modules_install"
> 
> Not being a seasoned kernel builder, I really don't know what's wrong 
> and I was wondering if anybody here can tell me what's up.

The problem you are seein is that symbols of the built modules do not
resolve to kernel symbols. This can have several reasons. One simple one
is that those modules indeed reference something that isn't there
(anymore).
The second one is that your build symbol tables have become confused.
This may happen when patching kernel and/or modifying the kernel
configuration. This can be resolved by doing (inside the toplevel kernel
directory):
	mv .config ..
	make mrproper
	mv ../.config .
	make oldconfig
	make dep
	make bzImage modules modules_install

This helped me several times ;)

And last but not least the brute force method... unless you need those
modules, simply remove them from /lib/modules/* :)

> TIA
> sjb
CU
  nils

> cd /lib/modules/2.4.20; \
> mkdir -p pcmcia; \
> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{}
> pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map 
> 2.4.20; fi depmod: *** Unresolved symbols in 
> /lib/modules/2.4.20/kernel/drivers/mtd/maps/sc520cdp.o
> depmod:         mtd_concat_create_R606fc87b
> depmod:         mtd_concat_destroy_R9c645004
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.20/kernel/drivers/net/wan/comx.o
> depmod:         proc_get_inode
> 

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

  parent reply	other threads:[~2003-05-26 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26  9:44 compile problem sjb
     [not found] ` <3ED1E212.30108-XuTx12Z7TonQT0dZR+AlfA@public.gmane.org>
2003-05-26 16:13   ` Nils Faerber [this message]
     [not found]     ` <20030526181327.21984b10.nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
2003-05-26 17:16       ` sjb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030526181327.21984b10.nils@kernelconcepts.de \
    --to=nils-t93ne7xhvje5bsectf/tx7nah6klmebb@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ottaky-XuTx12Z7TonQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox