public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <ml@basmevissen.nl>
To: rob@landley.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Make modules_install doesn't create /lib/modules/$version
Date: Fri, 19 Sep 2003 10:41:01 +0200	[thread overview]
Message-ID: <3F6AC11D.40103@basmevissen.nl> (raw)
In-Reply-To: <200309180321.40307.rob@landley.net>

Rob Landley wrote:

> I've installed -test3, -test4, and now -test5, and each time make 
> modules_install died with the following error:
> 
> Kernel: arch/i386/boot/bzImage is ready
> sh arch/i386/boot/install.sh 2.6.0-test5 arch/i386/boot/bzImage System.map ""
> /lib/modules/2.6.0-test5 is not a directory.
> mkinitrd failed
> make[1]: *** [install] Error 1
> make: *** [install] Error 2
> 
> I had to create the directory in question by hand, and then run it again, at 
> which point it worked.
> 
> Am I the only person this is happening for?  (Bog standard Red Hat 9 system 
> otherwise.  With Rusty's modutils...)
> 

I didn't see that here with Red Hat 9 system and 2.6.0-test3.

Maybe you can greb the used scripts to see which one does make (or test 
the existence of) the directory.

I now use the modutils package from rawhide. It also handles the 
creation of the new /etc/modprobe.conf file.

Bas.




  parent reply	other threads:[~2003-09-19  8:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18  7:21 Make modules_install doesn't create /lib/modules/$version Rob Landley
2003-09-18 16:15 ` Randy.Dunlap
2003-09-19  2:25   ` Rusty Russell
2003-09-19  5:41     ` Martin Schlemmer
2003-09-19  9:10       ` Mikael Pettersson
2003-09-19 16:01         ` Martin Schlemmer
2003-09-19 19:16           ` Rob Landley
2003-09-19 19:04     ` Rob Landley
2003-09-18 17:54 ` Sam Ravnborg
2003-09-19  8:41 ` Bas Mevissen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-19 21:39 Mikael Pettersson
2003-09-22 10:55 ` Rob Landley
2003-09-22 12:05   ` Mikael Pettersson
2003-09-22 13:02   ` Martin Schlemmer

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=3F6AC11D.40103@basmevissen.nl \
    --to=ml@basmevissen.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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