public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: walt <wa1ter@myrealbox.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.5-bk]  'modules_install' failed to install modules
Date: Wed, 14 Apr 2004 18:00:10 +0100	[thread overview]
Message-ID: <20040414170010.GA23419@redhat.com> (raw)
In-Reply-To: <20040414161827.GA2229@mars.ravnborg.org>

On Wed, Apr 14, 2004 at 06:18:27PM +0200, Sam Ravnborg wrote:
 > On Wed, Apr 14, 2004 at 08:40:47AM -0700, walt wrote:
 > > I pulled the latest changesets just now and found this weird behavior:
 > > 
 > > 'make' and 'make install' worked as expected, but 'make modules_install'
 > > just deleted all the old modules, ran depmod, and then installed no new
 > > modules -- nothing.
 > > 
 > > I finally found that doing another 'make' fixed whatever the problem
 > > was and allowed modules_install to work properly the second time.
 > > 
 > > This happened on two different machines, so I'm fairly sure it wasn't
 > > just me having a brainfart.
 > 
 > This is my second report about this.
 > But you gave some new info "work properly the second time".
 > This was not the case for the other person.

Make this the third.  I just saw it happen here too.
'make bzImage ; make modules ; make modules_install' fails in the above way.
Doing a 'make' seems to work.

		Dave

  parent reply	other threads:[~2004-04-14 17:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 15:40 [2.6.5-bk] 'modules_install' failed to install modules walt
2004-04-14 16:18 ` Sam Ravnborg
2004-04-14 16:43   ` Gene Heskett
2004-04-14 17:00   ` Dave Jones [this message]
2004-04-14 19:10     ` Gene Heskett
2004-04-14 20:25     ` Sam Ravnborg
2004-04-14 20:42       ` Dave Jones
2004-04-15  5:12       ` Simon Fowler
2004-04-15 14:55         ` Sam Ravnborg
2004-04-15  4:47     ` Simon Fowler

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=20040414170010.GA23419@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa1ter@myrealbox.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