public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Karel Kulhavý" <clock@twibright.com>
To: linux-kernel@vger.kernel.org
Subject: Re: make in 2.6.x
Date: Fri, 23 Jan 2004 15:20:45 +0000	[thread overview]
Message-ID: <20040123152045.C1130@beton.cybernet.src> (raw)
In-Reply-To: <20040123100035.73bee41f.jeremy@kerneltrap.org>; from jeremy@kerneltrap.org on Fri, Jan 23, 2004 at 10:00:35AM -0500

On Fri, Jan 23, 2004 at 10:00:35AM -0500, Jeremy Andrews wrote:
> > Is it correct to issue "make bzImage modules modules_install"
> > or do I have to do make bzImage; make modules modules_install?
> > 
> > Is there any documentation where I can read answer to this question?
> 
> make help
> 
> Cheers,
>  -Jeremy

I have read make help and skimmed through README however what I learned is
that the sequence "make bzImage ; make modules ; make modules_install" is
correct, but found no approval or disapproval for
"make bzImage modules modules_install"

Cl<

  parent reply	other threads:[~2004-01-23 15:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 14:50 make in 2.6.x Karel Kulhavý
2004-01-23 15:11 ` Bas Mevissen
     [not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
2004-01-23 15:13   ` gcc 2.95.3 Karel Kulhavý
2004-01-23 16:03     ` Daniel Andersen
     [not found]     ` <001b01c3e1ca$26101f20$1e00000a@black>
2004-01-23 16:30       ` Karel Kulhavý
2004-01-23 18:33         ` Matthew Reppert
2004-01-23 23:20           ` Stef van der Made
2004-01-24  0:48             ` Russell King
2004-01-26 14:41               ` David Woodhouse
2004-01-24 12:46             ` Ingo Buescher
2004-01-24 18:32               ` Stef van der Made
2004-01-23 18:55     ` Felipe Alfaro Solana
2004-01-25 11:05     ` Florian Weimer
2004-01-23 15:20   ` Karel Kulhavý [this message]
2004-01-23 15:20 ` make in 2.6.x Sam Ravnborg
2004-01-23 15:39   ` David Woodhouse
2004-01-23 17:42 ` Wakko Warner
2004-01-23 20:32   ` 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=20040123152045.C1130@beton.cybernet.src \
    --to=clock@twibright.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