All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: 3.9-rc1: hz.bc compilation breakage
Date: Thu, 07 Mar 2013 11:42:21 +0100	[thread overview]
Message-ID: <51386F0D.8060105@free-electrons.com> (raw)
In-Reply-To: <51380C65.50202@zytor.com>

Hi,

Le 07/03/2013 04:41, H. Peter Anvin a écrit :
> On 03/06/2013 06:36 AM, Maxime Ripard wrote:
>> I'm compiling the kernel for an iMX28(ARM) board, and since 3.9-rc1, I
>> get the following error at compilation time:
>>
>> make[3]: *** No rule to make target
>> `/home/max/Work/2012/crystalfontz/rewrite/linux-dt/include/config/hz.h',
>> needed by `kernel/hz.bc'.  Stop.
>>
>> I'm doing a clean out-of-tree build, with the following configuration
>> file: http://code.bulix.org/m4y7se-83102?raw
>>
>> Reverting commit 1b66e0fd ("kernel: Replace timeconst.pl with a bc
>> script") make the compilation go on as usual.
>>
> 
> That file should have been created by "make *config", and I just
> verified that it does indeed do so.  That file is a sentinel for
> configuration changes; the entire build system depends on it.

I triggered this issue when switching to 3.9-rc1, and oldconfig runs at
that time, and now, running menuconfig doesn't generates it either.

> I am not sure what you mean with "clean out-of-tree", however.

make O=$(pwd) -C /path/to/linux/source some_configs
make

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-03-07 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 14:36 3.9-rc1: hz.bc compilation breakage Maxime Ripard
2013-03-07  3:41 ` H. Peter Anvin
2013-03-07 10:42   ` Maxime Ripard [this message]
2013-03-07 15:06     ` H. Peter Anvin
2013-03-07 15:55       ` Maxime Ripard

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=51386F0D.8060105@free-electrons.com \
    --to=maxime.ripard@free-electrons.com \
    --cc=hpa@zytor.com \
    --cc=linux-kbuild@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.