Commit 858805b336be1cabb3d9033adaa3676574d12e37 ("kbuild: add $(BASH) to
run scripts with bash-extension") breaks my kernel test flow that targets
the HiFive Unleashed board. The boot traps during BBL early boot and
stops. QEMU is unaffected. Reverting 858805b336be fixes the issue.
I haven't yet had the opportunity to root-cause the issue. The issue may
be related to idiosyncracies in my local boot testing process, rather
than this commit.
- Paul
Hi Paul,
On Sat, Oct 5, 2019 at 2:48 AM Paul Walmsley <[email protected]> wrote:
>
>
> Commit 858805b336be1cabb3d9033adaa3676574d12e37 ("kbuild: add $(BASH) to
> run scripts with bash-extension") breaks my kernel test flow that targets
> the HiFive Unleashed board. The boot traps during BBL early boot and
> stops. QEMU is unaffected. Reverting 858805b336be fixes the issue.
The reason is because
a shell script using bash-extension is run by 'sh' instead of 'bash'.
Run 'git grep CONFIG_SHELL', then can you find a suspicious script?
Is there a warning/error message in the build log?
> I haven't yet had the opportunity to root-cause the issue. The issue may
> be related to idiosyncracies in my local boot testing process, rather
> than this commit.
>
>
> - Paul
--
Best Regards
Masahiro Yamada