Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] umip: Add new recipes
Date: Wed, 19 Nov 2014 16:49:12 +0100	[thread overview]
Message-ID: <20141119154912.GP3315@jama> (raw)
In-Reply-To: <1415353906-20924-1-git-send-email-qianl.fnst@cn.fujitsu.com>

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

On Fri, Nov 07, 2014 at 05:51:46PM +0800, Qian Lei wrote:
> UMIP is an open source implementation of Mobile IPv6 and NEMO Basic
> Support for Linux. It is released under the GPLv2 license. It supports
> the following IETF RFC: RFC6275 (Mobile IPv6), RFC3963 (NEMO), RFC3776
> and RFC4877 (IPsec and IKEv2).
> 
> Signed-off-by: Qian Lei <qianl.fnst@cn.fujitsu.com>
> ---
>  meta-oe/recipes-connectivity/umip/umip_1.0.bb | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>  create mode 100644 meta-oe/recipes-connectivity/umip/umip_1.0.bb
> 
> diff --git a/meta-oe/recipes-connectivity/umip/umip_1.0.bb b/meta-oe/recipes-connectivity/umip/umip_1.0.bb
> new file mode 100644
> index 0000000..a7163b0
> --- /dev/null
> +++ b/meta-oe/recipes-connectivity/umip/umip_1.0.bb
> @@ -0,0 +1,20 @@
> +SUMMARY = "Mobile IPv6 and NEMO for Linux"
> +DESCRIPTION = "UMIP is an open source implementation of Mobile IPv6 and NEMO \
> +Basic Support for Linux. It is released under the GPLv2 license. It supports \
> +the following IETF RFC: RFC6275 (Mobile IPv6), RFC3963 (NEMO), RFC3776 and \
> +RFC4877 (IPsec and IKEv2)."
> +
> +HOMEPAGE = "http://umip.org/"
> +SECTION = "System Environment/Base"
> +
> +SRC_URI = "git://git.umip.org/umip.git;tag=v${PV}"

Use SRCREV otherwise bitbake fetcher will always run git ls-remote to
map the tag to SRCREV.

> +DEPENDS = "rpm"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=073dc31ccb2ebed70db54f1e8aeb4c33"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit autotools-brokensep
> +
> +EXTRA_OE_CONF = "--enable-vt"

Missing some deps:

| In file included from conf_reload.c:36:0:
| conf.h:9:18: fatal error: pmgr.h: No such file or directory
|  #include "pmgr.h"
|                   ^


> -- 
> 1.8.4.2
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

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

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

  reply	other threads:[~2014-11-19 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  9:51 [PATCH] umip: Add new recipes Qian Lei
2014-11-19 15:49 ` Martin Jansa [this message]
2014-11-21  7:55   ` [PATCH v2 0/2] Add new recipe UMIP & Indent Qian Lei
2014-11-21  7:55     ` [PATCH v2 1/2] UMIP: add new recipe Qian Lei
2014-11-21 14:06       ` Joe MacDonald
2014-11-21 14:19         ` Martin Jansa
2014-11-21 14:46           ` Joe MacDonald
2014-11-25  9:23           ` Qian Lei
2014-11-21  7:55     ` [PATCH v2 2/2] Indent: Add " Qian Lei
2014-11-21  9:52       ` Martin Jansa
2014-11-24  5:21     ` [PATCH v3 1/2] indent: " Qian Lei
2014-11-24  5:28       ` [PATCH v3 2/2] UMIP: add " Qian Lei

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=20141119154912.GP3315@jama \
    --to=martin.jansa@gmail.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