From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot issue since 9 June 2021 ?
Date: Sun, 13 Jun 2021 12:11:42 +0300 [thread overview]
Message-ID: <87lf7e9lip.fsf@tarshish> (raw)
In-Reply-To: <CACaKL1wUo0VwDyXi--E6n-sdpbTtrzdr3XDdfHjgn4TV1D5=2w@mail.gmail.com>
Hi Jacques,
On Sun, Jun 13 2021, Jacques Samoun wrote:
> i noticed that, since Thurday 9th June, my BR based project could not build
> anymore.
> It seems that I was able to build till tag "2021.05" (and all the rc's
> before) but not anymore since then.
>
> My build fails on package MTD 2.1.2, where it could not install to target
>
> /bin/install -D -m 0755
> /home/jsadva/work/buildroot/output/build/mtd-2.1.2/ubihealthd
> /home/jsadva/buildroot/output/target/usr/sbin/ubihealthd
> /bin/install: cannot stat
> '/home/jsadva/work/buildroot/output/build/mtd-2.1.2/ubihealthd': No such
> file or directory
> make[1]: *** [package/pkg-generic.mk:341:
> /home/jsadva/work/buildroot/output/build/mtd-2.1.2/.stamp_target_installed]
> Error 1
>
> Of course, the buildroot "pull" is the only change to my environment,
> everything else unchanged (out of tree building)
> In the bug tracker, i saw a recently logged issue which is quite similar.
>
> Has somebody faced this recently ?
You might want to try this patch:
http://patchwork.ozlabs.org/project/buildroot/patch/20210609234819.1860554-2-mmayer at broadcom.com/
Or just enable BR2_PACKAGE_MTD_UBIFS_UTILS.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2021-06-13 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 9:00 [Buildroot] Buildroot issue since 9 June 2021 ? Jacques Samoun
2021-06-13 9:11 ` Baruch Siach [this message]
2021-06-13 9:45 ` Jacques Samoun
2021-06-13 10:00 ` Baruch Siach
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=87lf7e9lip.fsf@tarshish \
--to=baruch@tkos.co.il \
--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