mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: junkio@cox.net
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Documentation/modules.txt
Date: 04 Jan 2003 06:15:40 -0800	[thread overview]
Message-ID: <7v1y3typ9v.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <fa.gg57a2v.1j56o1v@ifi.uio.no>

>>>>> "SR" == Sam Ravnborg <sam@ravnborg.org> writes:

SR>  Anyway, your first step is to compile the kernel, as explained in the
SR>  file linux/README.  It generally goes like:
 
SR> -	make config
SR> -	make dep
SR> +	make *config <= usually menuconfig or xconfig
SR>  	make clean
SR>  	make zImage or make zlilo

If that is the case, this message after "make config" must go:

  *** End of Linux kernel configuration.
  *** Check the top-level Makefile for additional configuration.
  *** Next, you must run 'make dep'.

Here is a patch.

diff -u 2.4.20/scripts/Configure 2.4.20/scripts/Configure
--- 2.4.20/scripts/Configure	2001-07-02 13:56:40.000000000 -0700
+++ 2.4.20/scripts/Configure	2003-01-04 06:12:18.000000000 -0800
@@ -575,10 +575,7 @@
 echo
 echo "*** End of Linux kernel configuration."
 echo "*** Check the top-level Makefile for additional configuration."
-if [ ! -f .hdepend -o "$CONFIG_MODVERSIONS" = "y" ] ; then
-    echo "*** Next, you must run 'make dep'."
-else
-    echo "*** Next, you may run 'make bzImage', 'make bzdisk', or 'make install'."
+echo "*** Next, you may run 'make bzImage', 'make bzdisk', or 'make install'."
 fi
 echo


       reply	other threads:[~2003-01-04 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.gg57a2v.1j56o1v@ifi.uio.no>
2003-01-04 14:15 ` junkio [this message]
2003-01-04 14:32   ` Sam Ravnborg
2003-01-02 19:27 Sam Ravnborg
2003-01-02 19:54 ` Tomas Szepe
2003-01-02 20:05   ` Sam Ravnborg

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=7v1y3typ9v.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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

Powered by JetHome