Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] openconnect: add recipe
Date: Fri, 1 Apr 2016 13:27:04 +0200	[thread overview]
Message-ID: <20160401112704.GC2567@jama> (raw)
In-Reply-To: <1459171173-1527-1-git-send-email-adrian.ratiu@ni.com>

[-- Attachment #1: Type: text/plain, Size: 2517 bytes --]

On Mon, Mar 28, 2016 at 04:19:33PM +0300, Ioan-Adrian Ratiu wrote:
> openconnect is a FOSS VPN client designed to work with Cisco AnyConnect
> and Pulse Connect Secure (Juniper SSL).
> 
> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
> ---
>  .../recipes-connectivity/openconnect/openconnect_git.bb  | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>  create mode 100644 meta-networking/recipes-connectivity/openconnect/openconnect_git.bb
> 
> diff --git a/meta-networking/recipes-connectivity/openconnect/openconnect_git.bb b/meta-networking/recipes-connectivity/openconnect/openconnect_git.bb
> new file mode 100644
> index 0000000..241de30
> --- /dev/null
> +++ b/meta-networking/recipes-connectivity/openconnect/openconnect_git.bb
> @@ -0,0 +1,16 @@
> +SUMMARY = "Open client for Cisco AnyConnect VPN"
> +LICENSE = "LGPLv2.1"
> +LIC_FILES_CHKSUM = "file://COPYING.LGPL;md5=243b725d71bb5df4a1e5920b344b86ad"
> +
> +DEPENDS = "vpnc libxml2 gnutls"

It is trying to check vpnc-script on host:

| configure: Applying feature macros for GNU build
| configure: error: /etc/vpnc/vpnc-script does not seem to be executable.
|  OpenConnect will not function correctly without a vpnc-script.
|  See http://www.infradead.org/openconnect/vpnc-script.html for more details.
| 
|  If you are building a distribution package, please ensure that your
|  packaging is correct, and that a vpnc-script will be installed when the
|  user installs your package. You should provide a --with-vpnc-script=
|  argument to this configure script, giving the full path where the script
|  will be installed.
| 
|  The standard location is /etc/vpnc/vpnc-script. To bypass this error and
|  build OpenConnect to use the script from this location, even though it is
|  not present at the time you are building OpenConnect, pass the argument
|  "--with-vpnc-script=/etc/vpnc/vpnc-script"
| NOTE: The following config.log files may provide further information.
| WARNING: exit code 1 from a shell command.
| NOTE: /home/jenkins/anaconda/build-webos-wearable-master/build/BUILD/work/qemux86-webos-linux/openconnect/7.06-r0/build/config.log

> +
> +PV = "7.06"
> +
> +SRCREV = "35542d52202672b8c12ecc63867432128244013a"
> +SRC_URI = "git://git.infradead.org/users/dwmw2/openconnect.git"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit autotools pkgconfig
> +
> +EXTRA_OECONF += "--disable-static"
> -- 
> 2.7.4
> 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2016-04-01 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 13:19 [meta-oe][PATCH] openconnect: add recipe Ioan-Adrian Ratiu
2016-04-01 11:27 ` Martin Jansa [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=20160401112704.GC2567@jama \
    --to=martin.jansa@gmail.com \
    --cc=adrian.ratiu@ni.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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