From: Martin Bark <martin@barkynet.com>
To: buildroot@busybox.net
Subject: [Buildroot] Linux won't build any more?
Date: Tue, 04 Mar 2014 09:56:43 +0000 [thread overview]
Message-ID: <5315A35B.30204@barkynet.com> (raw)
In-Reply-To: <20140304090918.5eef0cd5@skate>
Thomas,
On 04/03/14 08:09, Thomas Petazzoni wrote:
> Dear Vincent Stehl?,
>
> On Tue, 4 Mar 2014 08:46:28 +0100, Vincent Stehl? wrote:
>
>> FYI I wonder if the recent commits on the master branch have not broken
>> linux kernel build in some cases. For example:
>>
>> $ make freescale_imx6sabresd_defconfig
>> $ make
>> linux/linux.mk:171: *** Configuration file
>> '/arch/arm/configs/imx6_defconfig' not found.. Stop.
>>
>> Same with qemu_arm_vexpress_defconfig.
>>
>> Git bisect points at commit b4cacbf5b15db06132b5f401d39b4c8d4e79158e,
>> "linux: check the configuration file exists". If I revert this commit
>> build will indeed still complain about the config but will go further.
>
> Thanks for the report. Do you still see this problem with the current
> Git head, including commits
> http://git.buildroot.net/buildroot/commit/?id=477c28cf1d637b224b819dd278103a05fb6f9dbb
> and
> http://git.buildroot.net/buildroot/commit/?id=4ad1ea59a59f951fad072dcb19429e6f468abf05 ?
>
> If you still see it, then I believe I'll just revert Yann's patches,
> they have caused too much troubles already.
>
> Again, thanks for your report!
>
> Thomas
>
I see this issue still, those two commit did not fix it. I noticed the
issue using raspberrypi_defconfig
$ make raspberrypi_defconfig
$ make
linux/linux.mk:171: *** Configuration file
'/arch/arm/configs/bcmrpi_quick_defconfig' not found.. Stop.
Thanks
Martin
next prev parent reply other threads:[~2014-03-04 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 7:46 [Buildroot] Linux won't build any more? Vincent Stehlé
2014-03-04 8:09 ` Thomas Petazzoni
2014-03-04 9:56 ` Martin Bark [this message]
2014-03-04 10:00 ` Fabio Porcedda
2014-03-04 13:10 ` Vincent Stehlé
2014-03-04 18:20 ` Thomas Petazzoni
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=5315A35B.30204@barkynet.com \
--to=martin@barkynet.com \
--cc=buildroot@busybox.net \
/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