mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: "make distclean" doesn't remove generated MLO file
Date: Tue, 7 Feb 2012 22:59:06 +0100	[thread overview]
Message-ID: <20120207215906.GE3852@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1202071200480.16867@oneiric>

On Tue, Feb 07, 2012 at 12:02:56PM -0500, Robert P. J. Day wrote:
> On Tue, 7 Feb 2012, Premi, Sanjeev wrote:
> 
> > I usually compile both stages together with a 'make clean' in
> > between, hence decided to preserve MLO. Makes it easy to copy both
> > MLO and barebox.bin at same time.
> 
>   is there any sort of requirement about cleaning in between those two
> steps?  if there is, that's a potential "gotcha" that should be
> clearly documented.

I'm not aware of any issues here. I only do a make clean when changing
the architecture.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2012-02-07 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 13:19 Robert P. J. Day
2012-02-07 16:34 ` Premi, Sanjeev
2012-02-07 16:44   ` Robert P. J. Day
2012-02-07 16:59     ` Premi, Sanjeev
2012-02-07 17:02       ` Robert P. J. Day
2012-02-07 17:05         ` Premi, Sanjeev
2012-02-07 17:07           ` Robert P. J. Day
2012-02-07 17:27             ` Premi, Sanjeev
2012-02-07 21:59         ` Sascha Hauer [this message]

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=20120207215906.GE3852@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=rpjday@crashcourse.ca \
    /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