mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: sha@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/2] fixup! Add security policy support
Date: Tue, 30 Sep 2025 11:35:27 +0200	[thread overview]
Message-ID: <20250930093532.2329023-1-a.fatoum@pengutronix.de> (raw)

Makefile: fix spurious find No such file or directory warnings

When building with:

  $ ./MAKEALL -O build-arm -a arm imx_v8_defconfig

we run into a couple of messages:

  Building arm64 imx_v8_defconfig
  Configure: OK
  find: ‘common’: No such file or directory
  find: ‘drivers’: No such file or directory
  find: ‘commands’: No such file or directory
  find: ‘lib’: No such file or directory
  [snip]

This is because the working directory during the run of MAKEALL is the
build directory, which at such an early time may not have these
directories yet.

Fix this by explicitly referencing the build directory while suppressing
the error.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 760ac28e8ff8..5d39261d7b74 100644
--- a/Makefile
+++ b/Makefile
@@ -1085,7 +1085,7 @@ $(sort $(BAREBOX_OBJS)) $(BAREBOX_LDS) $(BAREBOX_PBL_OBJS): $(barebox-dirs) ;
 
 PHONY += $(barebox-dirs)
 $(barebox-dirs): prepare scripts
-	@find $@ -name policy-list | xargs rm -f
+	@find $(objtree)/$@ -name policy-list -exec rm -f {} \; 2>/dev/null || true
 	$(Q)$(MAKE) $(build)=$@
 
 # Store (new) KERNELRELASE string in include/config/kernel.release
-- 
2.47.3




             reply	other threads:[~2025-09-30  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  9:35 Ahmad Fatoum [this message]
2025-09-30  9:35 ` [PATCH 2/2] fixup! test: py: add basic security policy test Ahmad Fatoum
2025-09-30  9:55 ` [PATCH 1/2] fixup! Add security policy support Sascha Hauer

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=20250930093532.2329023-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=sha@pengutronix.de \
    /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