From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 4/5] openvpn: still allow initV support
Date: Fri, 3 Sep 2021 16:16:59 +0200 [thread overview]
Message-ID: <20210903141659.GI4027748@pengutronix.de> (raw)
In-Reply-To: <20210812104015.19563-4-jbe@pengutronix.de>
On Thu, Aug 12, 2021 at 12:40:14PM +0200, Juergen Borleis wrote:
> Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
> ---
> rules/openvpn.make | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/rules/openvpn.make b/rules/openvpn.make
> index 46cca64..d5f2b81 100644
> --- a/rules/openvpn.make
> +++ b/rules/openvpn.make
> @@ -43,8 +43,11 @@ OPENVPN_CONF_ENV := \
> IFCONFIG=/usr/sbin/ifconfig \
> IPROUTE=/usr/sbin/ip \
> NETSTAT=/usr/bin/netstat \
> - ROUTE=/usr/sbin/route \
> - SYSTEMD_ASK_PASSWORD=/usr/bin/systemd-ask-password
> + ROUTE=/usr/sbin/route
> +
> +ifdef PTXCONF_OPENVPN_SYSTEMD
> +OPENVPN_CONF_ENV += SYSTEMD_ASK_PASSWORD=/usr/bin/systemd-ask-password
> +endif
What's the difference between not specifying SYSTEMD_ASK_PASSWORD and
/usr/bin/systemd-ask-password missing?
In other words, what happens if we build with
SYSTEMD_ASK_PASSWORD=/usr/bin/systemd-ask-password and systemd is not
actually used?
Will it try to find it at build-time anyways? Does it work differently at
runtime if no program is configured?
Michael
>
> #
> # autoconf
> --
> 2.20.1
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-09-03 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 10:40 [ptxdist] [PATCH 1/5] apache2: remove initV artefact Juergen Borleis
2021-08-12 10:40 ` [ptxdist] [PATCH 2/5] php: reanimate PHP as PHP8 Juergen Borleis
2021-08-12 11:15 ` Gieseler, Christian
2021-08-12 12:41 ` Juergen Borleis
2021-09-03 14:11 ` Michael Olbrich
2021-09-03 14:13 ` Michael Olbrich
2021-08-12 10:40 ` [ptxdist] [PATCH 3/5] lighttpd: reenable PHP support via "fast cgi" Juergen Borleis
2021-08-12 10:40 ` [ptxdist] [PATCH 4/5] openvpn: still allow initV support Juergen Borleis
2021-09-03 14:16 ` Michael Olbrich [this message]
2021-08-12 10:40 ` [ptxdist] [PATCH 5/5] openvpn: version bump 2.4.6 -> 2.5.3 Juergen Borleis
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=20210903141659.GI4027748@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=jbe@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