All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jahn Veach - Veachian64" <V64@Galaxy42.com>
To: <linux-kernel@vger.kernel.org>
Subject: Unresolved symbols in 2.4.6
Date: Sun, 8 Jul 2001 02:46:46 -0500	[thread overview]
Message-ID: <004e01c10782$250c71c0$66b93604@molybdenum> (raw)

I apologize in advance for bringing up a recently discussed problem and
being slightly off-topic, but I've been having problems similar to those in
"Unresolved symbols since 2.4.5 ?" from July 5.

I'm also running a Debian 2.2r3 box with kernel 2.2.17 and I've been having
trouble running 2.4.6 due to unresolved symbols in my modules brought up by
make modules_install. I had the latest version of modutils installed from
Adrian Bunk's Debian packages, which was the recommended fix in "Unresolved
symbols since 2.4.5 ?", but that didn't fix anything.

I tried compiling the kernel with gcc 2.95.2 and egcs-1.1.2 and I still get
the unresolved symbols. I used the Debian make-kpkg tool to make a kernel
image and I went through the process manually, but still I get the errors.

The output of depmod -e -a 2.4.6 can be found at
http://galaxy42.com/data/moderr.txt. I also have the recommended versions of
all software in linux/Documentation/Changes. To make things even more
puzzling, I have an almost identical box set up and it compiles just fine.

Does anyone know of anything that could possibly be causing this? Any help
is appreciated. If you have anything, please Cc: V64@Galaxy42.com. Thanks in
advance.

------
Jahn Veach - Veachian64 <V64@Galaxy42.com>
http://Galaxy42.com/

Well, let's just say, if your VCR is still blinking 12:00, you don't want
Linux.
--Bruce Perens



             reply	other threads:[~2001-07-08  7:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-08  7:46 Jahn Veach - Veachian64 [this message]
2001-07-08  8:23 ` Unresolved symbols in 2.4.6 Keith Owens
2001-07-08 14:20   ` Jahn Veach - Veachian64
2001-07-08 22:51     ` Keith Owens
2001-07-08 23:52       ` Jahn Veach - Veachian64
2001-07-09  0:37         ` Keith Owens
2001-07-09  1:46           ` Jahn Veach - Veachian64

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='004e01c10782$250c71c0$66b93604@molybdenum' \
    --to=v64@galaxy42.com \
    --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.