From: "Sven Püschel" <s.pueschel@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: [ptxdist] [PATCH] sockperf: don't run autogen.sh in sockperf.make
Date: Mon, 13 Oct 2025 18:35:01 +0200 [thread overview]
Message-ID: <20251013163527.2665822-2-s.pueschel@pengutronix.de> (raw)
When the configure file is missing from the project, an autogen.sh
should be added to patches instead of running autogen.sh in the prepare
stage.
Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
---
patches/sockperf-3.10/autogen.sh | 1 +
rules/sockperf.make | 6 ------
2 files changed, 1 insertion(+), 6 deletions(-)
create mode 120000 patches/sockperf-3.10/autogen.sh
diff --git a/patches/sockperf-3.10/autogen.sh b/patches/sockperf-3.10/autogen.sh
new file mode 120000
index 000000000..9f8a4cb7d
--- /dev/null
+++ b/patches/sockperf-3.10/autogen.sh
@@ -0,0 +1 @@
+../autogen.sh
\ No newline at end of file
diff --git a/rules/sockperf.make b/rules/sockperf.make
index 55b96875d..b1037c899 100644
--- a/rules/sockperf.make
+++ b/rules/sockperf.make
@@ -32,12 +32,6 @@ SOCKPERF_CONF_TOOL := autoconf
SOCKPERF_CONF_ENV := $(CROSS_ENV) GIT_CEILING_DIRECTORIES="$(BUILDDIR)"
SOCKPERF_MAKE_ENV := $(CROSS_ENV) GIT_CEILING_DIRECTORIES="$(BUILDDIR)"
-$(STATEDIR)/sockperf.prepare:
- @$(call targetinfo)
- @$(call world/execute, SOCKPERF, ./autogen.sh)
- @$(call world/prepare, SOCKPERF)
- @$(call touch)
-
# ----------------------------------------------------------------------------
# Target-Install
# ----------------------------------------------------------------------------
--
2.47.3
reply other threads:[~2025-10-13 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251013163527.2665822-2-s.pueschel@pengutronix.de \
--to=s.pueschel@pengutronix.de \
--cc=ptxdist@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