public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Orr <markorr@intersurf.com>
To: linux-kernel@vger.kernel.org
Subject: [2.4.15pre6] Funny error on "make modules_install" - cosmetic cleanup probably needed
Date: Mon, 19 Nov 2001 02:32:58 -0600	[thread overview]
Message-ID: <20011119023258.4bb705b0.markorr@intersurf.com> (raw)


I'm running 2.4.15-pre6 here, and for several previous
versions there's been an unusual (but harmless) error message
when installing modules via "make modules_install" once the
kernel build is done.

looks like this:

make[2]: Entering directory `/usr/src/linux/drivers/cdrom'
mkdir -p /lib/modules/2.4.15-pre6/kernel/drivers/cdrom/
cp cdrom.o cdrom.o /lib/modules/2.4.15-pre6/kernel/drivers/cdrom/
cp: will not overwrite just-created `/lib/modules/2.4.15-pre6/kernel/drivers/cdrom/cdrom.o' with `cdrom.o'
make[2]: *** [_modinst__] Error 1
make[2]: Leaving directory `/usr/src/linux/drivers/cdrom'
make[1]: *** [_modinst_cdrom] Error 2
make[1]: Leaving directory `/usr/src/linux/drivers'
make: *** [_modinst_drivers] Error 2

...As I say, it's harmless.  cdrom.o is getting installed, and
you can just make -i ... to get past it.

I'm guessing that I'm the only one getting this error (since I
cant find any other complaints about it)  because i'm using the
latest fileutils v4.1.1 off alpha.gnu.org, which must have code
to complain about such things -- but still, that

cp cdrom.o cdrom.o  /big/long/directory

...just looks weird.  Somebody leave something hanging in
one of the makefiles?

--
Mark Orr
markorr@intersurf.com



             reply	other threads:[~2001-11-19  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19  8:32 Mark Orr [this message]
2001-11-19 12:44 ` [2.4.15pre6] Funny error on "make modules_install" - cosmetic cleanup probably needed Keith Owens
2001-11-21 14:00   ` Todd M. Roy
2001-11-22 16:39     ` Jim Meyering

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=20011119023258.4bb705b0.markorr@intersurf.com \
    --to=markorr@intersurf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox