From 6dc138bad69cd666303e4ca3d72a2d0f7cf1ef1f Mon Sep 17 00:00:00 2001 From: Daniel Lenski Date: Sat, 22 Jan 2022 15:09:30 -0800 Subject: [PATCH] Build docs should mention that ./configure looks for vpnc-script in TWO places Thanks to Carston Allefeld for mentioning this in https://gitlab.com/openconnect/openconnect/-/issues/373#note_818605694 Signed-off-by: Daniel Lenski --- www/building.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/www/building.xml b/www/building.xml index aa4036ea..6fc7d2e0 100644 --- a/www/building.xml +++ b/www/building.xml @@ -47,14 +47,16 @@ on the command line.

OpenConnect should be given a default vpnc-script for network configuration (routing and DNS) at compile-time. This can be overridden at runtime (with --script).

-

The configure script will check whether /etc/vpnc/vpnc-script +

The configure script will check whether either + /etc/vpnc/vpnc-script or /usr/share/vpnc-scripts/vpnc-script exists and can be executed, and will fail if not. If you don't already have a copy then you should install one. It might be in a separate vpnc-script package for your operating system, it might be part of their vpnc package, and there's one linked from the vpnc-script page, if you need to download it manually. Install it as /etc/vpnc/vpnc-script.

-

If you do not want to use the standard location, you can configure OpenConnect to +

If you do not want to OpenConnect to use a vpnc-script from one of these + standard locations, you can configure OpenConnect to use a different location by default. When running the ./configure script in the instructions below, you can append an argument such as --with-vpnc-script=/where/I/put/vpnc-script to its command line. Note that the path you give will not be checked; the script doesn't have to be present when you build OpenConnect. But of course OpenConnect won't work very well without it, so you'll still have to install it later.

-- 2.50.1