mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] sockperf: don't run autogen.sh in sockperf.make
Date: Fri, 17 Oct 2025 10:21:04 +0200	[thread overview]
Message-ID: <20251017082104.3113194-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251013163527.2665822-2-s.pueschel@pengutronix.de>

Thanks, applied as deb15b25163b6d4e12ddb49a22bc308f62e5d327.

Michael

[sent from post-receive hook]

On Fri, 17 Oct 2025 10:21:04 +0200, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> 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>
> Message-Id: <20251013163527.2665822-2-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/patches/sockperf-3.10/autogen.sh b/patches/sockperf-3.10/autogen.sh
> new file mode 120000
> index 000000000000..9f8a4cb7ddcb
> --- /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 55b96875d5d4..b1037c899e95 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
>  # ----------------------------------------------------------------------------



      reply	other threads:[~2025-10-17  8:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 16:35 [ptxdist] [PATCH] " Sven Püschel
2025-10-17  8:21 ` Michael Olbrich [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=20251017082104.3113194-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=s.pueschel@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