mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: J Sloan <jjs@lexus.com>
To: rpjday <rpjday@mindspring.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.4.14 compiling fail for loop device
Date: Wed, 07 Nov 2001 13:44:27 -0800	[thread overview]
Message-ID: <3BE9AB3A.DFC6855F@lexus.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111070656540.4140-100000@localhost.localdomain>

rpjday wrote:

> On Wed, 7 Nov 2001, J Sloan wrote:
>
> > "Mohammad A. Haque" wrote:
> >
> > > On Wednesday, November 7, 2001, at 03:49 PM, Roeland Th. Jansen wrote:
> > >
> > > > when mounting an EFS cd on the loop it also froze. this is _without_
> > > > removing the lines. ...
> > >
> > > I'm a little confused. How did you even get a working kernel (or module)
> > > without removing the lines?
> > >
> >
> > Probably compiled it modular -
>
> if you try to compile it modular, the "make modules" will work, but
> the "make modules_install" will choke after copying the modules under
> /lib/modules when it tries to run the final "depmod" at the end.
>
> so, yes, i'm curious -- how did he get a final kernel and modules
> without removing those lines?

I got a kernel and modules without removing those
lines - it complains at depmod, but the kernel and
modules do build and install -

I didn't ever boot to that kernel since the warning
bothered me, and I fixed the source and recompiled
before booting into 2.4.14 -

cu

jjs


  reply	other threads:[~2001-11-07 21:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06  3:39 Terminator
2001-11-06  3:43 ` Mike Fedyk
2001-11-06  4:02 ` Robert Love
2001-11-06  4:08   ` Mohammad A. Haque
2001-11-06  4:14     ` Robert Love
2001-11-06  4:29       ` Mike Fedyk
2001-11-07 12:13     ` Todd M. Roy
2001-11-07 20:49       ` Roeland Th. Jansen
2001-11-07 21:11         ` Mohammad A. Haque
2001-11-07 21:34           ` J Sloan
2001-11-07 11:58             ` rpjday
2001-11-07 21:44               ` J Sloan [this message]
2001-11-07 21:41             ` Roeland Th. Jansen
2001-11-07 21:40           ` Roeland Th. Jansen
2001-11-07  3:13   ` Are -final releases realy FINAL? (Was Re: kernel 2.4.14 compiling fail for loop device) Anuradha Ratnaweera
2001-11-07  3:17     ` Mike Fedyk
2001-11-07  3:27       ` Anuradha Ratnaweera
2001-11-07  3:24     ` Michael H. Warfield
2001-11-07  4:06     ` David Lang
     [not found] <no.id>
2001-11-07 15:12 ` kernel 2.4.14 compiling fail for loop device Barry K. Nathan
2001-11-07 15:21   ` Todd M. Roy
2001-11-07 15:38   ` Mohammad A. Haque
2001-11-07 15:48     ` Mohammad A. Haque

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=3BE9AB3A.DFC6855F@lexus.com \
    --to=jjs@lexus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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

Powered by JetHome