mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, "Jürgen Kilb" <J.Kilb@phytec.de>
Subject: Re: make mrproper depends on a .config file?
Date: Mon, 4 Feb 2013 12:47:46 +0100	[thread overview]
Message-ID: <20130204114745.GA3366@x61s.8.8.8.8> (raw)
In-Reply-To: <20130204085226.GH1906@pengutronix.de>

On Mon, Feb 04, 2013 at 09:52:26AM +0100, Sascha Hauer wrote:
> On Fri, Feb 01, 2013 at 11:33:29AM +0100, Jürgen Kilb wrote:
> > Hi Sascha,
> > why does a "make mrproper" depends on a .config file?
> > 
> > It looks like commit 789fad984a11f63ad0728cd6eabad97b185dceea is
> > responsible...
> 
> Seems so, yes. I currently have no idea how to fix this. Reverting this
> commit is no solution. I tried to compare it with what the kernel does,
> but I have no clue what the problem is.
> 
> Sascha
>

I tried to figure out that with KBUILD_VERBOSE=1. It seems that "make
mrproper" will call:

"make -f $(PATH_TO_BAREBOX)/Makefile silentoldconfig"

at beginning of mrproper. I don't know why.

Regards Alex

> 
> -- 
> 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

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

      reply	other threads:[~2013-02-04 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 10:33 Jürgen Kilb
2013-02-04  8:52 ` Sascha Hauer
2013-02-04 11:47   ` Alexander Aring [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=20130204114745.GA3366@x61s.8.8.8.8 \
    --to=alex.aring@gmail.com \
    --cc=J.Kilb@phytec.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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