Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] merge_config.sh not working on out of tree builds since kconfig bump
Date: Mon, 29 Oct 2018 00:13:32 +0100	[thread overview]
Message-ID: <20181028231330.GA25011@x230> (raw)
In-Reply-To: <CAK4VdL0hEzyrMWJVXkokn+MrZpC=5pF-173OHVcGjT+O9W=OjQ@mail.gmail.com>

Hi Erico,

...
> $ make -C buildroot O=$PWD/output defconfig
> ...
> $ cd output
> $ echo 'BR2_TARGET_GENERIC_HOSTNAME="test"' > test.frag
> $ ../buildroot/support/kconfig/merge_config.sh .config test.frag
> Using .config as base
> Merging test.frag
> umask 0022 && make -C /home/test/buildroot O=/home/test/output/. alldefconfig
>   GEN     /home/test/output/Makefile
> *** Can't read seed configuration "./.tmp.config.qIcpASpUyh"!
> make[1]: *** [Makefile:925: alldefconfig] Error 1
> make: *** [Makefile:16: _all] Error 2


> I understand that kconfig is mostly ported from the kernel, but I
> don't know if this may be caused by any Buildroot customizations.
> I don't use merge_config.sh with the kernel but a simple attempt based
> on the above with 4.19-rc6 seems to work.
> The workaround seems to be to run merge_config.sh from the buildroot tree.
> Any clue?

Thanks for reporting bug. [1] patch from patchset [2] fixes that.
[1] https://patchwork.ozlabs.org/patch/990021/
[2] https://patchwork.ozlabs.org/project/buildroot/list/?series=72926&state=*


Kind regards,
Petr

      reply	other threads:[~2018-10-28 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 18:00 [Buildroot] merge_config.sh not working on out of tree builds since kconfig bump Erico Nunes
2018-10-28 23:13 ` Petr Vorel [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=20181028231330.GA25011@x230 \
    --to=petr.vorel@gmail.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