Re: [oe] [meta-qt5][PATCH] qtbase-native: nativesdk-qtbase: remove patch that breaks mkspec setting for SDK
On 17.02.2017 21:10, Martin Jansa wrote: On Thu, Feb 16, 2017 at 04:05:58PM +0100, Frieder Schrempf wrote: The patch 0008-configure-paths-for-target-qmake-properly.patch seems to be intended for the target, not for native/nativesdk, as it breaks the mkspec setting (sets linux-g++ instead of linux-oe-g++) by default. This issue is also described here: https://github.com/graugans/meta-udoo/issues/20#issuecomment-261241783 On which branch was this tested? It doesn't apply for master: OE @ ~/meta-qt5 $ pwam 137257 2017-02-17 21:07:37 URL:https://patchwork.openembedded.org/patch/137257/mbox/ [2388] -> "pw-am-137257.patch" [1] Applying: qtbase-native: nativesdk-qtbase: remove patch that breaks mkspec setting for SDK error: patch failed: recipes-qt/qt5/nativesdk-qtbase_git.bb:33 error: recipes-qt/qt5/nativesdk-qtbase_git.bb: patch does not apply error: patch failed: recipes-qt/qt5/qtbase-native_git.bb:28 error: recipes-qt/qt5/qtbase-native_git.bb: patch does not apply Patch failed at 0001 qtbase-native: nativesdk-qtbase: remove patch that breaks mkspec setting for SDK The copy of the patch that failed is found in: .git/rebase-apply/patch When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort". I've applied it manually for master, but next time please send patches rebased and tested on recent master. Sorry, it was based on morty. I will remember to rebase and test on master next time. Signed-off-by: Frieder Schrempf --- recipes-qt/qt5/nativesdk-qtbase_git.bb | 1 - recipes-qt/qt5/qtbase-native_git.bb| 1 - 2 files changed, 2 deletions(-) diff --git a/recipes-qt/qt5/nativesdk-qtbase_git.bb b/recipes-qt/qt5/nativesdk-qtbase_git.bb index 47e204b..e64c30e 100644 --- a/recipes-qt/qt5/nativesdk-qtbase_git.bb +++ b/recipes-qt/qt5/nativesdk-qtbase_git.bb @@ -33,7 +33,6 @@ SRC_URI += "\ file://0005-configure-bump-path-length-from-256-to-512-character.patch \ file://0006-QOpenGLPaintDevice-sub-area-support.patch \ file://0007-linux-oe-g-Invert-conditional-for-defining-QT_SOCKLE.patch \ -file://0008-configure-paths-for-target-qmake-properly.patch \ file://0009-Reorder-EGL-libraries-from-pkgconfig-and-defaults.patch \ file://0010-Pretend-Qt5-wasn-t-found-if-OE_QMAKE_PATH_EXTERNAL_H.patch \ " diff --git a/recipes-qt/qt5/qtbase-native_git.bb b/recipes-qt/qt5/qtbase-native_git.bb index ec4a9b6..c6a847a 100644 --- a/recipes-qt/qt5/qtbase-native_git.bb +++ b/recipes-qt/qt5/qtbase-native_git.bb @@ -28,7 +28,6 @@ SRC_URI += "\ file://0005-configure-bump-path-length-from-256-to-512-character.patch \ file://0006-QOpenGLPaintDevice-sub-area-support.patch \ file://0007-linux-oe-g-Invert-conditional-for-defining-QT_SOCKLE.patch \ -file://0008-configure-paths-for-target-qmake-properly.patch \ file://0009-Reorder-EGL-libraries-from-pkgconfig-and-defaults.patch \ file://0010-Pretend-Qt5-wasn-t-found-if-OE_QMAKE_PATH_EXTERNAL_H.patch \ " -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] OEDAM - Portland 2017
On 2/19/17 4:12 AM, Trevor Woerner wrote: > Does anyone have any recommendations for how to get from the > conference venue to the Mentor Graphics office? > I have a rental car and will have room for 2, or MAYBE 3 people. (At this point I suspect I will return the car after the OEDAM, because parting here is VERY expensive.) --Mark -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Splitting meta-oe?
[Re: [oe] Splitting meta-oe?] On 17.02.19 (Sun 19:31) Richard Purdie wrote: > On Fri, 2017-02-17 at 14:45 -0500, Philip Balister wrote: > > And I'm with these gyus. Splitting the git repository doesn't solve > > any underlying problems. The real problem from my point of view is > > very few of use are actually paid to maintain the layers we maintain. > > > > Employers want to pay things they profit from, and that is not paying > > someone to maintain "core infrastructure". > > > > Layer maintainers interests change over time, and you burn out > > supporting people who get to do all the cool stuff with the layers > > you maintain. In the end, you get all the crap and non of the glory. > > Within this list, most people appreciate your work. Outside the > > community, people completely underestimate the amount of work > > required to keep the ecosystem running. > > > > Yeah, add my name to the list of cranky people. > > I do think this is a valid question that Ross asks and that whilst the > first quick reaction is "no", its worth thinking about the pros/cons. Absolutely, and that's why I brought up earlier that my initial proposal for meta-networking was that it be a separate tree from the rest of meta-oe. When I first looked at this and what my initial goals were for meta-networking, it made sense to me to be at arms' length. Still does, to be honest, but being several years into the project now I find myself with a different mindset on the costs/benefits. > The pros to me would be about better test time on patches and in > theory more specialist knowledge. This isn't to say Martin/Joe don't > do a bad job but the size of meta-oe does mean there are limits. This is the thing that I'd like to get more of your point of view on, because it doesn't seem clear to me. Today, a quick survey of meta-oe shows we have 14 top-level layers in meta-oe (yeah, does seem like a lot) and of those I maintain one (sharing ownership with Armin when it comes to anything netkit-related, as noted in the MAINTAINERS file) of the others only meta-gnome seems to have only Martin listed as a maintainer (though a few, for example gpe, multimedia and oe, have only Martin and Koen, so there's certainly a case to be made there for there being a larger burden on them). Maybe we're talking specifically about meta-openembedded/meta-oe, in which case I apologize for derailing the discussion. I certain tried to help that situation with creating meta-networking and moving some of the stuff in meta-oe out into the new layer when we created it, but meta-oe still is a really big layer (664 recipes if 'find' can be trusted), no question. > The cons are more around finding suitable layer maintainers, which as > we all know are hard to find. > > I'd probably suggest that: > > a) We need to encourage/empower more people to maintain layers Yes, without question. > b) Having better infrastructure, tools and processes that help a) would > therefore be desirable. The updated patchwork has seriously made my life a lot easier. And I don't want to go off too much on an tangent, but I'd really love to bring meta-selinux into that same fold. > c) We need to be willing to separate out pieces for people to maintain > in such layers. It might not always work out but we should be > willing to try. This is the part I'm still struggling with. For good or ill meta-networking got created, I've tried to maintain it reasonably carefully and along the way the only thing that stands out for me as an issue while remaining part of the overall meta-openembedded project was a brief hiccup following the hardware upgrade at the end of December where I lost the ability to push commits. But since Martin hadn't, I just asked him to merge the meta-networking queue I was trying to merge and that's all sorted out now. I certainly don't object to having another meta-something in the overall meta-openembedded project and I don't object to having additional hands to carry the workload, but I'm not clear how separate git repositories addresses the current challenge. > As for the comments about core changes, I really do try hard not to > make them in many ways. The ones we do make, I'd hope are for the right > reasons. > > No easy answers but don't shoot Ross for asking what I think is a > reasonable question. I really, honestly did not mean for anything I said to sound like that. It's good to have this kind of discussion from time to time. It's very easy to get stuck in the "this is the way it's always been done" rut, so I hope Ross didn't feel like anyone was shouting him down. Wish I was going to be around Wilsonville this week, I'd like to talk more about this with you all. -- -Joe MacDonald. :wq signature.asc Description: Digital signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Splitting meta-oe?
On Fri, 2017-02-17 at 14:45 -0500, Philip Balister wrote: > And I'm with these gyus. Splitting the git repository doesn't solve > any underlying problems. The real problem from my point of view is > very few of use are actually paid to maintain the layers we maintain. > > Employers want to pay things they profit from, and that is not paying > someone to maintain "core infrastructure". > > Layer maintainers interests change over time, and you burn out > supporting people who get to do all the cool stuff with the layers > you maintain. In the end, you get all the crap and non of the glory. > Within this list, most people appreciate your work. Outside the > community, people completely underestimate the amount of work > required to keep the ecosystem running. > > Yeah, add my name to the list of cranky people. I do think this is a valid question that Ross asks and that whilst the first quick reaction is "no", its worth thinking about the pros/cons. The pros to me would be about better test time on patches and in theory more specialist knowledge. This isn't to say Martin/Joe don't do a bad job but the size of meta-oe does mean there are limits. The cons are more around finding suitable layer maintainers, which as we all know are hard to find. I'd probably suggest that: a) We need to encourage/empower more people to maintain layers b) Having better infrastructure, tools and processes that help a) would therefore be desirable. c) We need to be willing to separate out pieces for people to maintain in such layers. It might not always work out but we should be willing to try. As for the comments about core changes, I really do try hard not to make them in many ways. The ones we do make, I'd hope are for the right reasons. No easy answers but don't shoot Ross for asking what I think is a reasonable question. Cheers, Richard -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] OEDAM - Portland 2017
Okay thanks, sounds good. See you then. On Sun, Feb 19, 2017 at 5:49 PM, Philip Balister wrote: > It sounds like a bunch of us will meet in the Hilton lobby at 0800 and > use Lyft/Uber/other. > > Philip > > On 02/19/2017 07:12 AM, Trevor Woerner wrote: >> Does anyone have any recommendations for how to get from the >> conference venue to the Mentor Graphics office? >> > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH v2] netcat-openbsd: fix implicit dependency on pkg-config
In the report at http://errors.yoctoproject.org/Errors/Details/130673/
we see the following:
i586-oe-linux-gcc -m32 -march=i586 netcat.o atomicio.o socks.o
`pkg-config --libs libbsd` -lresolv -o nc
/bin/sh: 1: pkg-config: not found
What follows is a bunch of link errors for BSD library functions, as
the backtick didn't return anything but an empty string and hence no
BSD library was involved in the link.
I was able to reproduce this by temporarily removing my host version
of pkg-config, and then validated that this fix solves it while still
having the host binary removed. So it should fix the reported issue.
I also confirmed pkg-config was in the sysroot after the change.
Cc: Khem Raj
Cc: Martin Jansa
Signed-off-by: Paul Gortmaker
---
[v2: use inherit pkgconfig vs. depending on it, as per what
Khem suggested as being the more conventional route. ]
meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
b/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
index bb21e0cfeede..e0a0328eccfc 100644
--- a/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
+++ b/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
@@ -14,6 +14,8 @@ SRC_URI[netcat.sha256sum] =
"40653fe66c1516876b61b07e093d826e2a5463c5d994f1b7e6c
SRC_URI[netcat-patch.md5sum] = "e914f8eb7eda5c75c679dd77787ac76b"
SRC_URI[netcat-patch.sha256sum] =
"eee759327ffea293e81d0dde67921b7fcfcad279ffd7a2c9d037bbc8f882b363"
+inherit pkgconfig
+
S = "${WORKDIR}/${BPN}-${PV}"
EXTRA_OEMAKE += "'LDFLAGS=${LDFLAGS}'"
@@ -42,5 +44,3 @@ do_install() {
install -m 755 ${S}/nc ${D}${bindir}/nc.${BPN}
}
ALTERNATIVE_PRIORITY = "60"
-
-PNBLACKLIST[netcat-openbsd] ?= "Fails to build with RSS
http://errors.yoctoproject.org/Errors/Details/130673/";
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] are you allowed to have an underscore in a recipes directory?
On Sun, Feb 19, 2017 at 10:37 AM Robert P. J. Day wrote: > > i just noticed this in meta-oe/recipes-support: > > $ ls > ... > lm_sensors Its directory name I believe and not recipe name that you are talking about here in this case it is fine > > ... > > is there any issue with that directory name containing an > underscore? i know that has special meaning in a recipe file name, but > i've never noticed an underscore being used as above. > > rday > > -- > > > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > > > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] netcat-openbsd: fix implicit dependency on pkg-config
[Re: [oe] [PATCH] netcat-openbsd: fix implicit dependency on pkg-config] On
19/02/2017 (Sun 06:07) Khem Raj wrote:
> On Sat, Feb 18, 2017 at 5:12 PM Paul Gortmaker
> wrote:
>
[...]
> >
> > -DEPENDS += "glib-2.0 libbsd"
> > +DEPENDS += "glib-2.0 libbsd pkgconfig-native"
>
>
> I think inherit pkgconfig should be the way to go here
That seems reasonable and would explain why I wasn't seeing a lot of
pre-existing depends on pkgconfig. I'll test that and send a v2.
Thanks,
Paul.
--
>
> >
> >
> > SRC_URI =
> > "${DEBIAN_MIRROR}/main/n/netcat-openbsd/netcat-openbsd_${PV}.orig.tar.gz;name=netcat
> > \
> >
> > ${DEBIAN_MIRROR}/main/n/netcat-openbsd/netcat-openbsd_${PV}-7.debian.tar.gz;name=netcat-patch"
> > @@ -42,5 +42,3 @@ do_install() {
> > install -m 755 ${S}/nc ${D}${bindir}/nc.${BPN}
> > }
> > ALTERNATIVE_PRIORITY = "60"
> > -
> > -PNBLACKLIST[netcat-openbsd] ?= "Fails to build with RSS
> > http://errors.yoctoproject.org/Errors/Details/130673/";
> > --
> > 2.7.4
> >
> > --
> > ___
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> --
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] OEDAM - Portland 2017
It sounds like a bunch of us will meet in the Hilton lobby at 0800 and use Lyft/Uber/other. Philip On 02/19/2017 07:12 AM, Trevor Woerner wrote: > Does anyone have any recommendations for how to get from the > conference venue to the Mentor Graphics office? > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 2/3] remove blacklist entries against blacklisted gstreamer
florence, gthumb, farsight2 are failing:
http://lists.openembedded.org/pipermail/openembedded-core/2017-February/132936.html
On Wed, Feb 15, 2017 at 7:03 PM, Paul Gortmaker <
paul.gortma...@windriver.com> wrote:
> With gstreamer now fixed, we can remove all the blacklist entries
> against it.
>
> Signed-off-by: Paul Gortmaker
> ---
> meta-gnome/recipes-apps/cheese/cheese_2.30.1.bb|
> 2 --
> meta-gnome/recipes-gnome/gthumb/gthumb_2.12.4.bb |
> 3 ---
> meta-gnome/recipes-support/florence/florence_0.5.4.bb |
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-fluendo-mp3_0.10.31.bb |
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-fluendo-mpegdemux_0.10.85.bb |
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-meta-base_0.10.bb|
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-openmax_0.10.1.bb|
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-plugins-bad_0.10.23.bb |
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-plugins-base_0.10.36.bb |
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-plugins-gl_0.10.3.bb |
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-plugins-good_0.10.31.bb |
> 2 --
> .../recipes-multimedia/gstreamer-0.10/gst-plugins-ugly_0.10.19.bb |
> 2 --
> meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-rtsp_0.10.8.bb |
> 2 --
> meta-oe/recipes-support/farsight/farsight2_0.0.22.bb |
> 1 -
> meta-oe/recipes-support/farsight/libnice_0.0.13.bb |
> 2 --
> 15 files changed, 30 deletions(-)
>
> diff --git a/meta-gnome/recipes-apps/cheese/cheese_2.30.1.bb
> b/meta-gnome/recipes-apps/cheese/cheese_2.30.1.bb
> index 682c6fa26f6b..4be29ac67934 100644
> --- a/meta-gnome/recipes-apps/cheese/cheese_2.30.1.bb
> +++ b/meta-gnome/recipes-apps/cheese/cheese_2.30.1.bb
> @@ -21,6 +21,4 @@ do_configure_prepend() {
> sed -i -e "s: help : :g" ${S}/Makefile.am
> }
>
> -PNBLACKLIST[cheese] ?= "Depends on blacklisted gstreamer"
> -
> PNBLACKLIST[cheese] ?= "Depends on blacklisted gnome-desktop"
> diff --git a/meta-gnome/recipes-gnome/gthumb/gthumb_2.12.4.bb
> b/meta-gnome/recipes-gnome/gthumb/gthumb_2.12.4.bb
> index 94a14c818f10..4a1313c544c2 100644
> --- a/meta-gnome/recipes-gnome/gthumb/gthumb_2.12.4.bb
> +++ b/meta-gnome/recipes-gnome/gthumb/gthumb_2.12.4.bb
> @@ -30,6 +30,3 @@ FILES_${PN} += "${libdir}/${BPN}/extensions/*.so \
> ${libdir}/${BPN}/extensions/*.extension"
> FILES_${PN}-dev += "${libdir}/${BPN}/extensions/*.la"
> FILES_${PN}-dbg += "${libdir}/${BPN}/extensions/.debug/"
> -
> -
> -PNBLACKLIST[gthumb] ?= "Depends on blacklisted gstreamer"
> diff --git a/meta-gnome/recipes-support/florence/florence_0.5.4.bb
> b/meta-gnome/recipes-support/florence/florence_0.5.4.bb
> index d7e5b095944d..dfdb6bdb8c4d 100644
> --- a/meta-gnome/recipes-support/florence/florence_0.5.4.bb
> +++ b/meta-gnome/recipes-support/florence/florence_0.5.4.bb
> @@ -18,5 +18,3 @@ SRC_URI[sha256sum] = "26d33aa20d5fbf34ceeded4c41cb92
> 2d2988b6082e33d9acc46dd7bfe5
> inherit gettext autotools gconf pkgconfig
>
> EXTRA_OECONF = "--disable-scrollkeeper --without-docs --without-at-spi
> --without-panelapplet --without-xrecord"
> -
> -PNBLACKLIST[florence] ?= "Depends on blacklisted gstreamer"
> diff --git a/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> fluendo-mp3_0.10.31.bb b/meta-multimedia/recipes-
> multimedia/gstreamer-0.10/gst-fluendo-mp3_0.10.31.bb
> index e7c7c21dac9f..1e2cd2a4ab79 100644
> --- a/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> fluendo-mp3_0.10.31.bb
> +++ b/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> fluendo-mp3_0.10.31.bb
> @@ -12,5 +12,3 @@ acpaths = "-I ${S}/common/m4 -I ${S}/m4"
>
> SRC_URI[md5sum] = "adf0390f3416bb72f91c358528be0c38"
> SRC_URI[sha256sum] = "dae0d0559a4e159c0dd92b7e18de05
> 9a5783f8d038904c7de4ca6393f7d55c7d"
> -
> -PNBLACKLIST[gst-fluendo-mp3] ?= "Depends on blacklisted gstreamer"
> diff --git a/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> fluendo-mpegdemux_0.10.85.bb b/meta-multimedia/recipes-
> multimedia/gstreamer-0.10/gst-fluendo-mpegdemux_0.10.85.bb
> index 9787dbae724a..7bba41a34165 100644
> --- a/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> fluendo-mpegdemux_0.10.85.bb
> +++ b/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> fluendo-mpegdemux_0.10.85.bb
> @@ -10,5 +10,3 @@ acpaths = "-I ${S}/common/m4 -I ${S}/m4"
>
> SRC_URI[md5sum] = "7c4fb993f80b9ae631b11897733f0970"
> SRC_URI[sha256sum] = "df04c91cc8e5d9a892c2492ed98997
> 4b4547beaa2a3647649e85113317897424"
> -
> -PNBLACKLIST[gst-fluendo-mpegdemux] ?= "Depends on blacklisted gstreamer"
> diff --git a/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> meta-base_0.10.bb b/meta-multimedia/recipes-multimedia/gstreamer-0.10/gst-
> meta-base_0.10.bb
> index afd6a58a8c93..039abe14fa0f 100644
> --- a/meta-multimedia/recipes-multimedia/gstreamer-0.1
Re: [oe] [PATCH 3/3] farsight/xfce4-mixer: unblacklist recipes
farsight2 is still failing:
http://lists.openembedded.org/pipermail/openembedded-core/2017-February/132936.html
On Wed, Feb 15, 2017 at 7:03 PM, Paul Gortmaker <
paul.gortma...@windriver.com> wrote:
> These were 3rd level fallout from gstreamer being blacklisted, as
> they depended on packages that depended on gstreamer.
>
> Signed-off-by: Paul Gortmaker
> ---
> meta-oe/recipes-support/farsight/farsight2_0.0.22.bb | 3 ---
> meta-xfce/recipes-apps/xfce4-mixer/xfce4-mixer_4.11.0.bb | 2 --
> 2 files changed, 5 deletions(-)
>
> diff --git a/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
> b/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
> index 8c783a9f4770..2989850e9875 100644
> --- a/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
> +++ b/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
> @@ -28,6 +28,3 @@ FILES_${PN}-dbg += "${libdir}/*/.debug"
>
> SRC_URI[md5sum] = "e1f540cf3ebab06c3d7db1f46b44ac88"
> SRC_URI[sha256sum] = "3ae59aa61a8071c9fad111e5fd606a
> abc27961eb4192f8729987a27dae6b3974"
> -
> -PNBLACKLIST[farsight2] ?= "Depends on blacklisted libnice"
> -PNBLACKLIST[farsight2] ?= "Depends on blacklisted gst-plugins-base"
> diff --git a/meta-xfce/recipes-apps/xfce4-mixer/xfce4-mixer_4.11.0.bb
> b/meta-xfce/recipes-apps/xfce4-mixer/xfce4-mixer_4.11.0.bb
> index 2c91fa9b930e..bdbec458bc47 100644
> --- a/meta-xfce/recipes-apps/xfce4-mixer/xfce4-mixer_4.11.0.bb
> +++ b/meta-xfce/recipes-apps/xfce4-mixer/xfce4-mixer_4.11.0.bb
> @@ -12,5 +12,3 @@ SRC_URI[md5sum] = "1b3753b91224867a3a2dfddda239c28d"
> SRC_URI[sha256sum] = "fb0c1df201ed1130f54f15b914cbe5
> a59286e994a137acda5609570c57112de2"
>
> RDEPENDS_${PN} = "gst-meta-audio"
> -
> -PNBLACKLIST[xfce4-mixer] ?= "Depends on blacklisted gst-plugins-base"
> --
> 2.7.4
>
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] efivar: update to 0.30 to fix readdir* issues
The native version is now failing:
http://lists.openembedded.org/pipermail/openembedded-core/2017-February/132936.html
On Fri, Feb 17, 2017 at 9:11 AM, Koen Kooi wrote:
> Drop patches with upstream fixes.
>
> Signed-off-by: Koen Kooi
> ---
> .../efivar/efivar/0002-disable-static-build.patch | 33
> .../0004-fix-unknow-option-for-gold-linker.patch | 38
> --
> .../fix-compile-failure-with-host-gcc-4.6.patch| 45
> --
> .../efivar/{efivar_0.24.bb => efivar_0.30.bb} | 8 +---
> 4 files changed, 2 insertions(+), 122 deletions(-)
> delete mode 100644 meta-oe/recipes-extended/efivar/efivar/0002-disable-
> static-build.patch
> delete mode 100644 meta-oe/recipes-extended/
> efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch
> delete mode 100644 meta-oe/recipes-extended/efivar/efivar/fix-compile-
> failure-with-host-gcc-4.6.patch
> rename meta-oe/recipes-extended/efivar/{efivar_0.24.bb => efivar_0.30.bb}
> (72%)
>
> diff --git
> a/meta-oe/recipes-extended/efivar/efivar/0002-disable-static-build.patch
> b/meta-oe/recipes-extended/efivar/efivar/0002-disable-static-build.patch
> deleted file mode 100644
> index 951b159..000
> --- a/meta-oe/recipes-extended/efivar/efivar/0002-disable-
> static-build.patch
> +++ /dev/null
> @@ -1,33 +0,0 @@
> -From 126e0d3c1ad74cf5b0abe9e98ec444bcc3c83159 Mon Sep 17 00:00:00 2001
> -From: Koen Kooi
> -Date: Fri, 4 Mar 2016 14:53:55 +0100
> -Subject: [PATCH 2/2] disable static build
> -
> -Signed-off-by: Koen Kooi
> -
> -Upstream-Status: Inappropriate [meta-oe specific]
> -Signed-off-by: Hongxu Jia
> -
>
> - src/Makefile | 4 ++--
> - 1 file changed, 2 insertions(+), 2 deletions(-)
> -
> -diff --git a/src/Makefile b/src/Makefile
> -index 1829d22..c7a0ca3 100644
> a/src/Makefile
> -+++ b/src/Makefile
> -@@ -8,9 +8,9 @@ include $(TOPDIR)/Make.defaults
> -
> - LIBTARGETS=libefivar.so libefiboot.so
> - STATICLIBTARGETS=libefivar.a libefiboot.a
> --BINTARGETS=efivar efivar-static
> -+BINTARGETS=efivar
> - PCTARGETS=efivar.pc efiboot.pc
> --TARGETS=$(LIBTARGETS) $(STATICLIBTARGETS) $(BINTARGETS) $(PCTARGETS)
> -+TARGETS=$(LIBTARGETS) $(BINTARGETS) $(PCTARGETS)
> -
> - LIBEFIBOOT_SOURCES = crc32.c creator.c disk.c gpt.c linux.c loadopt.c
> - LIBEFIBOOT_OBJECTS = $(patsubst %.c,%.o,$(LIBEFIBOOT_SOURCES))
> ---
> -2.4.3
> -
> diff --git
> a/meta-oe/recipes-extended/efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch
> b/meta-oe/recipes-extended/efivar/efivar/0004-fix-unknow-
> option-for-gold-linker.patch
> deleted file mode 100644
> index 5d50c19..000
> --- a/meta-oe/recipes-extended/efivar/efivar/0004-fix-unknow-
> option-for-gold-linker.patch
> +++ /dev/null
> @@ -1,38 +0,0 @@
> -From b3d35e7dd27a755df5acbe050837885914dbb28b Mon Sep 17 00:00:00 2001
> -From: Hongxu Jia
> -Date: Tue, 10 May 2016 11:34:50 -0400
> -Subject: [PATCH] fix unknow option for gold linker
> -
> -- Revert the following patch, since oe-core work with gcc 5
> -...
> -commit 3055a3797f16693dfdd855fa68bc57fd900dc408
> -Author: Peter Jones
> -Date: Mon Feb 15 14:15:40 2016 -0500
> -
> -Make gcc.specs work with gcc 6 / binutils 2.26
> -
> -Apparently binutils 2.26 gets real picky about "ld -PIC" vs "ld
> -fPIC".
> -
> -Signed-off-by: Peter Jones
> -...
> -
> -- Remove unknown option '--add-needed'
> -
> -Signed-off-by: Hongxu Jia
>
> - gcc.specs | 2 +-
> - 1 file changed, 1 insertion(+), 1 deletion(-)
> -
> -diff --git a/gcc.specs b/gcc.specs
> -index 24fabc2..5b0fdef 100644
> a/gcc.specs
> -+++ b/gcc.specs
> -@@ -14,4 +14,4 @@
> - + %{!shared:%{!static:%{!r:-pie}}} %{static:-Wl,-no-fatal-warnings
> -Wl,-static -static -Wl,-z,relro,-z,now}
> -
> - *link:
> --+ %{!static:--fatal-warnings} --no-undefined-version
> --no-allow-shlib-undefined --add-needed -z now --build-id
> %{!static:%{!shared:-PIE}} %{shared:-z relro -PIC} %{static:% -++ %{!static:--fatal-warnings} --no-undefined-version
> --no-allow-shlib-undefined -z now --build-id %{!static:%{!shared:-pie}}
> %{shared:-z relro -fPIC} %{static:% ---
> -2.8.1
> -
> diff --git a/meta-oe/recipes-extended/efivar/efivar/fix-compile-
> failure-with-host-gcc-4.6.patch b/meta-oe/recipes-extended/
> efivar/efivar/fix-compile-failure-with-host-gcc-4.6.patch
> deleted file mode 100644
> index 1c68a29..000
> --- a/meta-oe/recipes-extended/efivar/efivar/fix-compile-
> failure-with-host-gcc-4.6.patch
> +++ /dev/null
> @@ -1,45 +0,0 @@
> -From 1361225abbaba878960f970df39a4570bbc39553 Mon Sep 17 00:00:00 2001
> -From: Hongxu Jia
> -Date: Thu, 26 May 2016 21:50:01 -0400
> -Subject: [PATCH] fix compile failure with older host gcc (<=4.6)
> -
> -While host gcc version is 4.6.3 in ubuntu 1204, it
> -did not recognize -std=gnu11 and -Wmaybe-uninitialized.
> -
> -While host gcc version is 4.4.7 in centos6, it
> -did not recognize -std=gnu11, -Wmaybe-uninitialized,
> -and -flto.
> -
> -For native build, use -std=gnu99 to replace -std=gnu11,
> -and directly
[oe] State of bitbake world, Failed tasks 2017-02-18
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed
depencencies !!|Signatures!!colspan='12'|QA
!!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
||qemuarm||max||min ||qemux86||max||min ||all
||already-stripped ||libdir||textrel ||build-deps
||file-rdeps||version-going-backwards ||host-user-contaminated
||installed-vs-shipped ||unknown-configure-option ||symlink-to-sysroot
||invalid-pkgconfig ||pkgname ||
|-
||2017-02-18||5 ||6 ||5 ||N/A ||N/A ||N/A ||N/A ||N/A
||N/A ||0 ||0 ||0 ||3 ||1
||5 ||2144 ||0 ||0 ||0
||0 ||0 ||0 ||
|}
http://www.openembedded.org/wiki/Bitbake_World_Status
== Failed tasks 2017-02-18 ==
INFO: jenkins-job.sh-1.8.17 Complete log available at
http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170219_095431.log
=== common (5) ===
*
meta-openembedded/meta-gnome/recipes-gnome/gthumb/gthumb_2.12.4.bb:do_configure
*
meta-openembedded/meta-gnome/recipes-support/florence/florence_0.5.4.bb:do_configure
*
meta-openembedded/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb:do_configure
*
meta-smartphone/meta-android/recipes-android/android-tools/android-tools_4.2.2.bb:do_compile
*
virtual:native:meta-openembedded/meta-oe/recipes-extended/efivar/efivar_0.30.bb:do_compile
=== common-x86 (0) ===
=== qemuarm (0) ===
=== qemux86 (1) ===
*
meta-browser/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb:do_compile
=== qemux86_64 (0) ===
=== Number of failed tasks (16) ===
{| class=wikitable
|-
|| qemuarm || 5 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemuarm.20170217_163325.log/
|| http://errors.yoctoproject.org/Errors/Build/32678/
|-
|| qemux86 || 6 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemux86.20170217_153048.log/
|| http://errors.yoctoproject.org/Errors/Build/32679/
|-
|| qemux86_64 || 5 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemux86-64.20170218_121122.log/
|| http://errors.yoctoproject.org/Errors/Build/32693/
|}
=== PNBLACKLISTs (421) ===
=== QA issues (2153) ===
{| class=wikitable
!| Count||Issue
|-
||0 ||already-stripped
|-
||0 ||host-user-contaminated
|-
||0 ||installed-vs-shipped
|-
||0 ||invalid-pkgconfig
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||symlink-to-sysroot
|-
||0 ||unknown-configure-option
|-
||1 ||build-deps
|-
||2144 ||version-going-backwards
|-
||3 ||textrel
|-
||5 ||file-rdeps
|}
=== Incorrect PACKAGE_ARCH or sstate signatures (0) ===
Complete log:
http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.signatures.20170218_120426.log/
No issues detected
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] are you allowed to have an underscore in a recipes directory?
i just noticed this in meta-oe/recipes-support: $ ls ... lm_sensors ... is there any issue with that directory name containing an underscore? i know that has special meaning in a recipe file name, but i've never noticed an underscore being used as above. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] OEDAM - Portland 2017
I think some folks where going to try to get a ride share from the HIlton hotel. -M On Sun, Feb 19, 2017 at 4:12 AM, Trevor Woerner wrote: > Does anyone have any recommendations for how to get from the > conference venue to the Mentor Graphics office? > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] OEDAM - Portland 2017
Does anyone have any recommendations for how to get from the conference venue to the Mentor Graphics office? -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [morty][meta-openembedded] Commit backport required
Damn .. you are right. Poky was accidentally set to use the master branch instead of morty. Nevermind my posting then. On 2017-02-18 21:27, Martin Jansa wrote: Are you sure you're using right version of bitbake? I doubt that bb.data API changes was backported to release branch of bitbake. On Sat, Feb 18, 2017 at 9:08 PM, Carlos Rafael Giani wrote: Hello, commit d361ef01a9a61cd8a83f7728f7d3e9f118233cb8 "nis, opencv: Update getVar/setVar syntax" needs to be backported to meta-openembedded's morty branch. Otherwise builds break, because the deprecated bb.data API was removed also in morty. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
