All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: newbie list <linux-newbie@vger.kernel.org>
Subject: Re: Multi-kernel in grub
Date: Tue, 22 Jul 2003 19:20:03 -0700	[thread overview]
Message-ID: <5.1.0.14.1.20030722181649.0201cdf0@celine> (raw)
In-Reply-To: <1058910886.2992.10.camel@localhost.localdomain>

OK. This clears up a lot. Since the "make bzImage" step fails, everything 
that follows it is irrelevant to your problem. And *this* is where your 
problem occurs, not when trying to cp or mv the file created by "make bzImage".

A basic rule that beginners need to learn: when a step in the process fails 
with error messages, going on to the next step is almost always wasted effort.

The next basic rule: believe the error messages. In your case, you get an 
error that says:

"make[3]: *** No rule to make target 
`/usr/src/linux-2.4.20-8/drivers/pci/devlist.h', needed by `names.o'.  Stop."

Unfortunately, I do not have a fresh kernel source tree handy to unpack, so 
I do not know *for sure* if this file really gets generated by the make 
process ... but it does appear to be a generated file from its internal 
structure and timestamps here. So I suspect the problem is that you did not 
follow carefully enough the steps needed to compile a kernel, and that this 
error just happens to be the first place where your omission matters.

As I assume you know, the outline of how to compile a kernel is in the 
source tree in /[path-to-source-tree]/README . A quick, compact review of 
the steps is:

         make mrproper [not always needed]
         make clean [not always needed]
         make config
           -OR-
         make menuconfig
           -OR-
         make xconfig
         make dep
         make bzImage
         make modules
         make install [or install by hand]
         make modules_install

This sequence is a bit more extended than the one you say you followed, so 
first off, follow it and see if it fixes your problem. If not, report back 
with the step it first fails on and what the error message looks like (as 
you did before).


At 04:54 PM 7/22/2003 -0500, Travis Osterman wrote:
>I tried to compile my kernel again and here are the results.  I'm really
>new to this, and thank you for your patience.
>
># make dep // no errors
># make clean: // no errors
># make bzImage // below
>
>make[3]: *** No rule to make target
>`/usr/src/linux-2.4.20-8/drivers/pci/devlist
>.h', needed by `names.o'.  Stop.
>make[3]: Leaving directory `/usr/src/linux-2.4.20-8/drivers/pci'
>make[2]: *** [first_rule] Error 2
>make[2]: Leaving directory `/usr/src/linux-2.4.20-8/drivers/pci'
>make[1]: *** [_subdir_pci] Error 2
>make[1]: Leaving directory `/usr/src/linux-2.4.20-8/drivers'
>make: *** [_dir_drivers] Error 2

[rest deleted]

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs

  reply	other threads:[~2003-07-23  2:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 15:15 Multi-kernel in grub Travis
2003-07-22 15:19 ` /cdrom fails to unmount Dan Zlotnikov
2003-07-22 15:44   ` Amin
2003-07-22 16:06   ` pa3gcu
2003-07-22 15:43 ` Multi-kernel in grub Amin
     [not found] ` <Pine.LNX.4.43.0307221116460.20338-100000@perpugilliam.cscl ub.uwaterloo.ca>
2003-07-22 15:58   ` /cdrom fails to unmount Ray Olszewski
2003-07-22 16:28     ` Dan Zlotnikov
2003-07-23 14:58       ` pa3gcu
2003-07-22 16:11 ` Multi-kernel in grub pa3gcu
2003-07-22 21:54 ` Travis Osterman
2003-07-23  2:20   ` Ray Olszewski [this message]
2003-07-23  4:51     ` Travis Osterman
2003-07-23  6:24       ` pa3gcu
2003-07-24  3:20         ` Travis Osterman
2003-07-24  7:54           ` Julien Didron
2003-07-24 12:32           ` pa3gcu

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=5.1.0.14.1.20030722181649.0201cdf0@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.