From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Joe Kellner <jdk@kingsmeadefarm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: clean before or after dep?
Date: Sun, 8 Sep 2002 14:53:06 +0100 [thread overview]
Message-ID: <20020908135306.GB701@gallifrey> (raw)
In-Reply-To: <1031491886.3d7b512ec36fc@webmail.kingsmeadefarm.com>
* Joe Kellner (jdk@kingsmeadefarm.com) wrote:
> Currently, what is the proper way then? I know over the years the proper
> procedure has changed. make *config; make dep; make clean; make *Image;make
> modules?
I always do
make clean && make dep && make ......
Notes:
1) I've always done clean and then dep ever since a problem on Alpha
where it created a file during dep and deleted it in clean.
2) I always use && instead of ; - that way if one of the stages fails
you don't miss it.
3) The ..... - some architectures like zImage, some like Image, some
like boot; hell I can never remember which a particular platform
needs. I wish we had some commonality (hmm - an 'itso' target).
4) Generally make {menu|x}config tells you the story for x86 at the
end.
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2002-09-08 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 1:51 D. Hugh Redelmeier
2002-09-08 13:13 ` Alan Cox
2002-09-08 13:31 ` Joe Kellner
2002-09-08 13:53 ` Dr. David Alan Gilbert [this message]
2002-09-09 18:03 ` Thunder from the hill
2002-09-08 14:53 ` Sam Ravnborg
2002-09-08 17:51 ` Thomas Molina
2002-09-08 18:09 ` D. Hugh Redelmeier
2002-09-08 18:50 ` Sam Ravnborg
2002-09-08 18:54 ` jbradford
2002-09-08 19:23 ` Sam Ravnborg
2002-09-09 7:29 ` Helge Hafting
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=20020908135306.GB701@gallifrey \
--to=gilbertd@treblig.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jdk@kingsmeadefarm.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
all inboxes | Powered by JetHome®