From: Thom Borton <borton@phys.ethz.ch>
To: Peter Romba <promba@purdue.edu>, linux-kernel@vger.kernel.org
Subject: Re: Help a newbie: "make modules_install" causes depmod errors for EVERY module on EVERY kernel I try?
Date: Sat, 18 Oct 2003 17:16:15 +0200 [thread overview]
Message-ID: <200310181716.15557.borton@phys.ethz.ch> (raw)
In-Reply-To: <3F9002FA.6030709@purdue.edu>
What's the compiler version you use? Try gcc -v. If it's a 3.xx, then
the kernel won't compile properly. If I am not mistaken, 2.95.4 is
recommended.
Yours, Thom
On Friday 17 October 2003 16:55, Peter Romba wrote:
> For some reason I can't compile a kernel anymore. I recently
> installed gnome 2.4 from source (the only major system change I can
> think of). Now when I try to compile 2.4.21, make modules_install
> gives depmod errors for EVERY module, even dummy.o in the case of
> an out-of-the-box kernel configuration. This behavior happens on
> every kernel that I've tried. This is using the typical make
> mrproper, make menuconfig, make dep, make clean, make bzImage, make
> modules, make modules_install sequence of stuff.
>
> In the process of building gnome I had to update ld from an RPM
> (couldn't install it from source, e-mail me if you want details on
> that).
>
> Any help would be greatly appreciated :)... I'm at a loss about
> what to do.
>
> --Peter
> promba@purdue.edu
>
> -
> 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/
--
Thom Borton
Switzerland
prev parent reply other threads:[~2003-10-18 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 14:55 Help a newbie: "make modules_install" causes depmod errors for EVERY module on EVERY kernel I try? Peter Romba
2003-10-17 15:39 ` DervishD
2003-10-18 15:16 ` Thom Borton [this message]
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=200310181716.15557.borton@phys.ethz.ch \
--to=borton@phys.ethz.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=promba@purdue.edu \
/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