From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 04/11] gpsd, foxtrotgps: blacklist, fails to build with new binutils-2.27
Date: Wed, 31 Aug 2016 21:40:59 +0200 [thread overview]
Message-ID: <20160831194106.14065-4-Martin.Jansa@gmail.com> (raw)
In-Reply-To: <20160831194106.14065-1-Martin.Jansa@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb | 3 ++-
meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb | 3 +++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb b/meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb
index d91cbcb..32b20c3 100644
--- a/meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb
+++ b/meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb
@@ -6,7 +6,8 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"
DEPENDS = "curl gtk+ libglade sqlite3 libexif gpsd bluez4 intltool-native"
-PNBLACKLIST[foxtrotgps] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
+PNBLACKLIST[foxtrotgps] ?= "Depends on broken gpsd"
+#PNBLACKLIST[foxtrotgps] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez5', 'bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES', '', d)}"
SRC_URI = "http://www.foxtrotgps.org/releases/${BP}.tar.gz"
SRC_URI[md5sum] = "6777d448ee9d3ba195f9d26ea90e3163"
diff --git a/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb b/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb
index 6b883a8..822fc24 100644
--- a/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb
+++ b/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb
@@ -137,3 +137,6 @@ RPROVIDES_${PN} += "${PN}-systemd"
RREPLACES_${PN} += "${PN}-systemd"
RCONFLICTS_${PN} += "${PN}-systemd"
SYSTEMD_SERVICE_${PN} = "${PN}.socket"
+
+# http://errors.yoctoproject.org/Errors/Details/81000/
+PNBLACKLIST[gpsd] ?= "BROKEN: fails to build with new binutils 2.27"
--
2.9.2
next prev parent reply other threads:[~2016-08-31 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 19:40 [meta-oe][PATCH 01/11] xf86-input-tslib: remove Martin Jansa
2016-08-31 19:40 ` [meta-oe][PATCH 02/11] efl: remove dependency on tslib Martin Jansa
2016-08-31 19:40 ` [meta-oe][PATCH 03/11] directfb: add PACKAGECONFIG for inputdrivers Martin Jansa
2016-08-31 19:40 ` Martin Jansa [this message]
2016-08-31 19:41 ` [meta-oe][PATCH 05/11] gnome-menus, gnome-panel3, gnome-control-center: blacklist, gnome-menus fails to build because of python Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 06/11] accel-ppp: blacklist, fails to build with new binutils-2.27 Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 07/11] samba: " Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 08/11] glmark2: blacklist, fails to build with gcc-6 Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 09/11] tracker: blacklist, fails to build with new binutils-2.27 Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 10/11] geany-plugins: blacklist because of QA issues Martin Jansa
2016-08-31 21:16 ` Andreas Müller
2016-08-31 19:41 ` [meta-oe][PATCH 11/11] smbnetfs: blacklist, depends on broken samba Martin Jansa
2016-09-04 4:03 ` [meta-oe][PATCH 01/11] xf86-input-tslib: remove Jonathan Liu
2016-09-04 10:06 ` Martin Jansa
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=20160831194106.14065-4-Martin.Jansa@gmail.com \
--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