mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Jürgen Kilb" <J.Kilb@phytec.de>
To: barebox@lists.infradead.org, Sascha Hauer <s.hauer@pengutronix.de>
Subject: make mrproper depends on a .config file?
Date: Fri, 01 Feb 2013 11:33:29 +0100	[thread overview]
Message-ID: <510B99F9.9000801@phytec.de> (raw)

Hi Sascha,
why does a "make mrproper" depends on a .config file?

It looks like commit 789fad984a11f63ad0728cd6eabad97b185dceea is 
responsible...

If there is a valid .config file, the problem doesn't pop up.

====
barebox-2013.01.0$ make ARCH=arm 
CROSS_COMPILE=/opt/OSELAS.Toolchain-2012.12.0/arm-cortexa9-linux-gnueabi/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/bin/arm-cortexa9-linux-gnueabi- 
mrproper
make -f scripts/Makefile.clean obj=arch/arm/pbl
   HOSTCC  scripts/basic/fixdep
   HOSTCC  scripts/basic/docproc
   HOSTCC  scripts/kconfig/conf.o
   SHIPPED scripts/kconfig/zconf.tab.c
   SHIPPED scripts/kconfig/zconf.lex.c
   SHIPPED scripts/kconfig/zconf.hash.c
   HOSTCC  scripts/kconfig/zconf.tab.o
   HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[3]: *** [silentoldconfig] Fehler 1
make[2]: *** [silentoldconfig] Fehler 2
   CLEAN   scripts/basic
   CLEAN   scripts/kconfig
barebox-2013.01.0$
===

greetings,
Jürgen

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

             reply	other threads:[~2013-02-01 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 10:33 Jürgen Kilb [this message]
2013-02-04  8:52 ` Sascha Hauer
2013-02-04 11:47   ` Alexander Aring

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=510B99F9.9000801@phytec.de \
    --to=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