All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <ml@basmevissen.nl>
To: jarausch@belgacom.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.14-pre7 Unresolved symbols
Date: Wed, 17 Sep 2003 16:08:47 +0200	[thread overview]
Message-ID: <3F686AEF.1000900@basmevissen.nl> (raw)
In-Reply-To: <20030917095232.CC86AA7E68@numa-i.igpm.rwth-aachen.de>

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.



  reply	other threads:[~2003-09-17 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 10:53 2.4.14-pre7 Unresolved symbols jarausch
2003-09-17 14:08 ` Bas Mevissen [this message]
2003-09-17 14:11   ` Bas Mevissen
  -- strict thread matches above, loose matches on Subject: below --
2001-11-02 10:53 jarausch
2001-11-02 11:22 ` Sebastian Dröge
2001-11-02 18:51   ` Michael H. Warfield
2001-11-02 19:38     ` J Sloan
2001-11-02 10:53 jarausch
2001-11-02 10:53 jarausch
2003-09-17 16:49 ` Richard B. Johnson

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=3F686AEF.1000900@basmevissen.nl \
    --to=ml@basmevissen.nl \
    --cc=jarausch@belgacom.net \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.