From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 7/9] libsecret: remove the recipe due to its move to oe-core
Date: Mon, 14 Sep 2015 15:26:46 +0300 [thread overview]
Message-ID: <1442233610-32279-7-git-send-email-alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <1442233610-32279-1-git-send-email-alexander.kanavin@linux.intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
.../recipes-gnome/libsecret/libsecret_0.18.bb | 23 ----------------------
1 file changed, 23 deletions(-)
delete mode 100644 meta-gnome/recipes-gnome/libsecret/libsecret_0.18.bb
diff --git a/meta-gnome/recipes-gnome/libsecret/libsecret_0.18.bb b/meta-gnome/recipes-gnome/libsecret/libsecret_0.18.bb
deleted file mode 100644
index f610d44..0000000
--- a/meta-gnome/recipes-gnome/libsecret/libsecret_0.18.bb
+++ /dev/null
@@ -1,23 +0,0 @@
-SUMMARY = "libsecret is a library for storing and retrieving passwords and other secrets"
-LICENSE = "LGPLv2.1"
-LIC_FILES_CHKSUM = "file://COPYING;md5=23c2a5e0106b99d75238986559bb5fc6"
-
-inherit gnomebase gtk-doc
-
-DEPENDS = "glib-2.0 libgcrypt"
-
-GNOME_COMPRESS_TYPE = "xz"
-
-EXTRA_OECONF += "--disable-manpages"
-
-SRC_URI[archive.md5sum] = "279d723cd005e80d1d304f74a3488acc"
-SRC_URI[archive.sha256sum] = "0c73aa762dbd1e38ba7b03de350e23ce818cb810b0784375e95ef61e004b02e3"
-
-# Fails to build with thumb-1 (qemuarm)
-# | {standard input}: Assembler messages:
-# | {standard input}:686: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#3'
-# | {standard input}:686: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#13'
-# | {standard input}:687: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#29'
-# | {standard input}:687: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#19'
-# | {standard input}:688: Error: lo register required -- `orr r10,r10,r10'
-ARM_INSTRUCTION_SET = "arm"
--
2.1.4
next prev parent reply other threads:[~2015-09-14 12:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 12:26 [PATCH 1/9] gsettings-desktop-schemas: remove the recipe due to its move to oe-core Alexander Kanavin
2015-09-14 12:26 ` [PATCH 2/9] gnome-desktop3: " Alexander Kanavin
2015-09-14 12:26 ` [PATCH 3/9] libwnck3: " Alexander Kanavin
2015-09-14 12:26 ` [PATCH 4/9] gcr: " Alexander Kanavin
2015-09-14 12:26 ` [PATCH 5/9] p11-kit: " Alexander Kanavin
2015-09-14 12:26 ` [PATCH 6/9] libwebp: " Alexander Kanavin
2015-09-14 12:26 ` Alexander Kanavin [this message]
2015-09-14 12:26 ` [PATCH 8/9] ruby: " Alexander Kanavin
2015-09-14 12:26 ` [PATCH 9/9] libyaml: " Alexander Kanavin
2015-09-14 12:26 ` [PATCH 10/10] epiphany: " Alexander Kanavin
2015-09-14 12:29 ` Alexander Kanavin
2015-09-14 12:26 ` [PATCH 10/10] libyaml: " Alexander Kanavin
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=1442233610-32279-7-git-send-email-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.