Message-ID: <3F686AEF.1000900@basmevissen.nl>
Date: Wed, 17 Sep 2003 16:08:47 +0200
From: Bas Mevissen <ml@basmevissen.nl>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: jarausch@belgacom.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.14-pre7 Unresolved symbols
References: <20030917095232.CC86AA7E68@numa-i.igpm.rwth-aachen.de>
In-Reply-To: <20030917095232.CC86AA7E68@numa-i.igpm.rwth-aachen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 980
Lines: 32

jarausch@belgacom.net wrote:
> Hi,
> 
> trying to build 2.4.14-pre7 breaks with the error message
> depmod: *** Unresolved symbols in /lib/modules/2.4.14-pre7/kernel/fs/romfs/romfs.o
> depmod:         unlock_page
> 
> during make modules_install.
> 
> 2.4.14-pre6 is running fine here.
> 

Why are you (still) using 2.4.14-preX? Current stable version is 2.4.22 
and 2.4.23-preX is under development.

Anyway, grep for "unlock_page" in all .c files, find out if the .o of it 
is built and if the symbol is exported with EXPORT_SYMBOL.

BTW. Did you save the .config file and ran "make mrproper" before 
building? It is very likely that after patching up in a "used" tree, the 
rebuild is not going entirely correctly.

Regards,

Bas.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/