From: "Alberto Manuel Brandão Simões" <albie@alfarrabio.di.uminho.pt>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems compiling kernel 2.4.22
Date: 03 Sep 2003 18:10:50 +0100 [thread overview]
Message-ID: <1062609049.860.4.camel@eremita.di.uminho.pt> (raw)
In-Reply-To: <Pine.LNX.4.53.0309031257410.28170@chaos>
On Wed, 2003-09-03 at 17:58, Richard B. Johnson wrote:
> On Wed, 3 Sep 2003, Alberto Manuel [ISO-8859-1] Brandão Simões wrote:
> > On Wed, 2003-09-03 at 17:28, Alberto Manuel Brandão Simões wrote:
> > > [1.] One line summary of the problem:
> > > modules symbols broken references
> > >
> > > [2.] Full description of the problem/report:
> > > when I make 'make modules_install' I get:
> > > depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/net/ipv4/ipip.o
> > > depmod: ip_send_check
> > > depmod: register_netdevice
> > > ..
> > >
> > > and so on, and not only for these modules: vfat, smbfs, msdos, etc
> > >
> > > By the way, when I tried to ssh to paste more information, I got in the
> > > console:
>
> [SNIPPED...]
>
> BYW. Did you try booting the new system, THEN, executing `depmod -a` ?
ok. In this case, it does not give any broken reference.
But, then, why does make modules_install run depmod if we know (almost
certain) that it will give broken references?
But, I need some more help. I can't load any ACPI modules, getting a No
such device as answer. I don't have also a /proc/acpi directory.
Thanks for any help.
Alberto
>
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
> Note 96.31% of all statistics are fiction.
>
>
next prev parent reply other threads:[~2003-09-03 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 16:28 Alberto Manuel Brandão Simões
2003-09-03 16:51 ` Alberto Manuel Brandão Simões
2003-09-03 16:58 ` Richard B. Johnson
2003-09-03 17:10 ` Alberto Manuel Brandão Simões [this message]
2003-09-03 17:28 ` 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=1062609049.860.4.camel@eremita.di.uminho.pt \
--to=albie@alfarrabio.di.uminho.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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
all inboxes | Powered by JetHome®