[oe] [meta-browser][PATCH 4/4] chromium-x11: update 48.0.2548.0 -> 52.0.2743.76

Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium-browser.inc | 1 + .../chromium/chromium-wayland_48.0.2548.0.bb | 9 +-- .../chromium/chromium-x11_48.0.2548.0.bb | 19 - .../chromium/chromium-x11_52.0.2743.76.bb

[oe] [meta-browser][PATCH 2/4] chromium: gcc-6 support

Allow chromium to build with gcc-6. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- ...0001-bignum.cc-disable-warning-from-gcc-5.patch | 60 --- ...-image_util.cc-disable-warning-from-gcc-5.patch | 39 -- .../0008-Fix-GCC-uninitialized-warning.patch

[oe] [meta-browser][PATCH 0/4] chromium updates

is considered the latest stable (as per https://www.chromium.org/developers/calendar) Trevor Woerner (4): chromium: remove unused patch chromium: gcc-6 support chromium: split into -wayland and -x11 chromium-x11: update 48.0.2548.0 -> 52.0.2743.76 recipes-browser/chromium/chromium-browser.

[oe] layerindex upvoting Was: [OE-core] OE Changelog since 2016-05-15 until 2016-05-22

On Fri 2016-05-27 @ 08:25:23 AM, Paul Eggleton wrote: > On Thu, 26 May 2016 22:18:34 Andreas Müller wrote: > > On Thu, May 26, 2016 at 10:14 PM, Paul Eggleton > > > > wrote: > > > On Thu, 26 May 2016 13:46:21 Cliff Brake wrote: > > >> On Tue, May 24, 2016 at 5:23

Re: [oe] [OE-core] Please help edit OEDAM minutes

On Fri 2016-05-13 @ 09:57:07 AM, Trevor Woerner wrote: > On Thu 2016-05-12 @ 04:32:01 PM, Jeff Osier-Mixon wrote: > > I admit defeat. I have been "trying to get to" the OEDAM minutes for a > > month and I am clearly not getting to it, so I am now getting out of > >

Re: [oe] [OE-core] Please help edit OEDAM minutes

On Thu 2016-05-12 @ 04:32:01 PM, Jeff Osier-Mixon wrote: > I admit defeat. I have been "trying to get to" the OEDAM minutes for a > month and I am clearly not getting to it, so I am now getting out of > the way. We are crowdsourcing these minutes, because collaborative > effort is what we do best.

Re: [oe] [meta-browsser] chromium issues

On Mon 2016-04-18 @ 11:37:19 AM, S. Lockwood-Childs wrote: > If you just plan on using chromium as a normal browser without such > bells and whistles, don't worry about the keys and get rid of the > warning by setting them as blank when you start up chromium > > export GOOGLE_API_KEY=" " > export

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2016-03-16

On Thu 2016-03-17 @ 03:43:57 PM, Martin Jansa wrote: > c278358 metadata-revs: provide more information I think the general consensus was to not accept patch c278358 since it affected the layout of a file that was expected to be processed by scripts. > e2bf30c buildhistory.bbclass: metadata-revs

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2016-03-09

On 03/10/16 06:53, Martin Jansa wrote: I'll look at cef3 and chromium issue, my recent patch for meta-browser fixed the build for armv7a MACHINEs, so it probably needs to be extended a bit to cover warnings in x86 and then duplicate the same to cef3. This issue is there for so long, slowing down

[oe] [meta-oe][PATCH] scsirastools: autotools_stage not required

The functionality of autotools_stage has been incorporated into autotools, so openembedded-core removed the autotools_stage class, therefore remove it here too. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- meta-oe/recipes-extended/scsirastools/scsirastools_1.6.4.bb | 2 +-

[oe] [meta-oe][PATCH] nodejs: upgrade from 4.2.4 to 4.2.6

...plus a switch to xz. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- .../recipes-devtools/nodejs/{nodejs_4.2.4.bb => nodejs_4.2.6.bb}| 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta-oe/recipes-devtools/nodejs/{nodejs_4.2.4.bb => nodejs_4.2.6.bb}

[oe] [meta-oe][PATCH v3] nodejs: update from 4.2.3 to 4.2.4

bsite and documentation, used with permission. -This program uses several Node.js modules contained in the node_modules/ +This program uses several Node modules contained in the node_modules/ subdirectory, according to the terms of their respective licenses. "

Re: [oe] [meta-browser][PATCH 2/3] chromium: update run script for early run

On 01/06/16 07:07, Koen Kooi wrote: > Op 05-01-16 om 22:15 schreef Trevor Woerner: > > If the chromium run-helper script (google-chrome) is run as part of a > > (sysvinit) init script, shell variables $USER and $HOME will not be set > > (leading to unwanted behaviour).

Re: [oe] [meta-oe][PATCH] dhcpcd: add recipe for dhcpcd

On 01/05/16 16:55, Stephen Arnold wrote: > My vote would be whatever is the most stable/reliable should be in > the core layers rather than an "extra" layer people need to add to > bblayers manually. But there's always "bitbake-layers add-layer" and "bitbake-layers layerindex-fetch" to help :-)

[oe] [meta-browser][PATCH 2/3] chromium: update run script for early run

the chromium run-helper script will work as expected in both instances (as part of an init script and from the cmdline). Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium/google-chrome | 4 ++-- recipes-browser/chromium/chromium_40.0.2214.91.bb | 3

[oe] [meta-browser][PATCH 3/3] chromium: add kiosk-mode PACKAGECONFIG

If you are creating a kiosk, then enable this PACKAGECONFIG and the browser will start up fullscreen and without menu bars etc. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium.inc | 1 + recipes-browser/chromium/chromium_40.0.2214.91.

[oe] [meta-browser][PATCH 1/3] chromium_40.0.2214.91: API keys update

Add more information to the "disable-api-keys-info-bar" PACKAGECONFIG description regarding another way to disable the "Google API keys are missing" warning. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium_40.0.2214.91.bb | 8 +

[oe] [meta-browser][PATCH] chromium_40.0.2214.91: API keys update

Add more information to the "disable-api-keys-info-bar" PACKAGECONFIG description regarding another way to disable the "Google API keys are missing" warning. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium_40.0.2214.91.bb | 8 +

Re: [oe] [meta-browser][RFC PATCH v1 3/4] chromium_40.0.2214.91: API keys update

Hi Otavio, On 01/04/16 05:53, Otavio Salvador wrote: > I applied the first two patches of this serie. Awesome, thanks! I'm working on v2 now. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org

Re: [oe] [meta-browser][RFC PATCH v1 4/4] chromium: upgrade 40.0.2214.91 to 49.0.2607.0

Carlos, I need to understand the intent of the patch "0001-Remove-accelerated-Canvas-support-from-blacklist.patch" you created for chromium-40. Back then the json block you wanted to remove for your builds was: { "id": 24, "description": "Accelerated 2d canvas is unstable in

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2016-01-01

On 01/02/16 13:19, Martin Jansa wrote: > > == Tested changes (not included in master yet) - meta-openembedded == ... > 7020a19 nodejs: cleanup and update ... > > == Failed tasks 2016-01-01 == ... > > === qemuarm (1) === > * /meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs_4.2.2.bb >

[oe] [meta-browser][RFC PATCH v1 0/4] chromium: update from 40.0.2214.91 to 49.0.2607.0

CHROMIUM_BUILD_TYPE: - Release - Debug PACKAGECONFIG options: - use-egl (on by default) - disable-api-keys-info-bar - component-build - ignore-lost-context - impl-side-painting Trevor Woerner (4): chromium.inc: fix typos chromium_40.0.2214.91.bb

[oe] [meta-browser][RFC PATCH v1 3/4] chromium_40.0.2214.91: API keys update

Add more information to the "disable-api-keys-info-bar" PACKAGECONFIG description regarding another way to disable the "Google API keys are missing" warning. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium_40.0.2214.91.bb

[oe] [meta-browser][RFC PATCH v1 4/4] chromium: upgrade 40.0.2214.91 to 49.0.2607.0

Upgrade chromium to the latest version. Cleanup the recipe somewhat and cleanup the patches. The only change in the LICENSE is the copyright year. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- ...4-Remove-hard-coded-values-for-CC-and-CXX.patch | 0 ...4-Remove-hard-coded-values-

[oe] [meta-browser][RFC PATCH v1 1/4] chromium.inc: fix typos

The gl PACKAGECONFIG is "use-egl", not "use-gl". Adjust comment to include a space after initial comment delimiter (#). Close parenthesis at end of comment. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium.inc | 4 ++-- 1 file c

[oe] [meta-browser][RFC PATCH v1 2/4] chromium_40.0.2214.91.bb: improve PACKAGECONFIG info

affected by PACKAGECONFIG options to be closer to where these options are listed and explained. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-browser/chromium/chromium_40.0.2214.91.bb | 81 +-- 1 file changed, 45 insertions(+), 36 deletions(-) diff

Re: [oe] [meta-browser][RFC PATCH v1 3/4] chromium_40.0.2214.91: API keys update

Oops, looks like this patch got messed up. My git rebase foo isn't as good as it should be ;-) On 01/01/16 14:45, Trevor Woerner wrote: > diff --git a/recipes-browser/chromium/chromium_49.0.2607.0.bb > b/recipes-browser/chromium/chromium_49.0.2607.0.bb > new file mode 100644 > i

Re: [oe] chromium 40.0.2214.91 doesn't like gcc5.3

The version of chromium we're using is a bit old (it's almost a year old now) and I thought that maybe a newer version might have the required fixes in it already. Along those lines I tried updating the recipe to build chromium-49.0.2607.0 which was released December 30, 2015. As it turned out

[oe] [meta-oe][PATCH] nodejs: update from 4.2.3 to 4.2.4

Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- .../recipes-devtools/nodejs/{nodejs_4.2.3.bb => nodejs_4.2.4.bb}| 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta-oe/recipes-devtools/nodejs/{nodejs_4.2.3.bb => nodejs_4.2.4.bb} (93%) diff --git a/met

Re: [oe] chromium 40.0.2214.91 doesn't like gcc5.3

On 12/30/15 11:52, Martin Jansa wrote: > On Wed, Dec 30, 2015 at 01:18:48AM -0500, Trevor Woerner wrote: >> I noticed the recent gcc update from 5.2 to 5.3 in openembedded-core >> seems to cause meta-browser's chromium build to fail with more warnings >> being treated

Re: [oe] chromium 40.0.2214.91 doesn't like gcc5.3

Hi Max, On 12/30/15 10:26, Max Krummenacher wrote: > Hi Trevor > > Am Mittwoch, den 30.12.2015, 01:18 -0500 schrieb Trevor Woerner: >> I noticed the recent gcc update from 5.2 to 5.3 in openembedded-core >> seems to cause meta-browser's chromium build to fail with more >

[oe] next bitbake world run and updates

Hi Martin, I'm hoping my nodejs_4.2.3.bb makes it into your next "State of bitbake world" run and passes this time. When do you think your next "bitbake world" will occur? I ask because since sending my v4 patches for nodejs_4.2.3, node-v4.2.4 has been released. Do I send the list a patch of the

Re: [oe] chromium 40.0.2214.91 doesn't like gcc5.3

Hi Khem, On 12/30/15 13:04, Khem Raj wrote: > can you backport and report back > > https://chromium.googlesource.com/v8/v8/+/e28183b5977a2d2732f7f8b9a2f26637c9566585%5E%21/#F0 That diff includes 4 patches: Index: src/bignum.cc Index: src/compiler/ia32/code-generator-ia32.cc Index:

[oe] [meta-oe][PATCH v2] nodejs: update from 4.2.3 to 4.2.4

m logo, the typeface, and trademarks - further text was added clarifying the separation between npm itself and the various npm packages, their data and licenses Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- .../recipes-devtools/nodejs/{nodejs_4.2.3.bb => nodejs_4.2.4.bb}| 6 +++---

Re: [oe] [meta-oe][PATCH v2] nodejs: update from 4.2.3 to 4.2.4

On 12/30/15 15:48, Khem Raj wrote: >> On Dec 30, 2015, at 12:06 PM, Trevor Woerner <twoer...@gmail.com> wrote: >> >> Additionally, the LICENSE file changed: Updated node LICENSE file with new >> npm >> license: >> >> - npm's license changed fro

Re: [oe] [meta-oe][PATCH v2] nodejs: update from 4.2.3 to 4.2.4

On 12/30/15 17:05, Khem Raj wrote: > Yes. please include exact diff instead of summarizing as your patch does. diff --git a/LICENSE b/LICENSE index 7920cbb..ea51cc4 100644 --- a/LICENSE +++ b/LICENSE @@ -338,11 +338,32 @@ The externally maintained libraries used by Node.js are: - npm is a

[oe] chromium 40.0.2214.91 doesn't like gcc5.3

I noticed the recent gcc update from 5.2 to 5.3 in openembedded-core seems to cause meta-browser's chromium build to fail with more warnings being treated as errors. My MACHINE is intel-corei7-64, but I'm guessing this probably happens on other architectures too. Is anyone looking at this? Is

Re: [oe] [meta-oe][PATCH v3 1/1] nodejs: cleanup and update

Hi Andre, On 12/22/15 04:35, Andre McCurdy wrote: > Here's the link to the "official" announcement about v8 dropping > support for ARM cores without vfp2 support: Thanks, I'll include that in v4. > +COMPATIBLE_MACHINE = "(-)" > +COMPATIBLE_MACHINE_x86 = "(.*)" > +COMPATIBLE_MACHINE_x86-64 =

[oe] [meta-oe][PATCH v4 0/1] nodejs cleanup and update

instead of whitelisting machines, blacklist the unsupported ones Changes from v2: handle qemuarm build failure Changes from v1: don't try to keep and unite the old recipe versions, just replace them with the latest stable Trevor Woerner (1): nodejs: cleanup and update .../nodejs

[oe] [meta-oe][PATCH v4 1/1] nodejs: cleanup and update

gcc no longer supports a VFPv2 option: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#index-mfpu-1460 Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- .../nodejs/nodejs/enable-armv5e-build.patch| 22 -- .../nodejs/nodejs4/libev-cross-cc_0.4.12.patch |

Re: [oe] [meta-oe][PATCH v4 1/1] nodejs: cleanup and update

Hi Andre, On 12/22/15 13:06, Andre McCurdy wrote: Remove old nodejs4_0.4.12 and update nodejs_0.12.7 to the latest stable nodejs_4.2.3. Nodejs is picky about which architectures it supports. The supported arch mapping required some updating to bring it up to date with the current nodejs code.

Re: [oe] [meta-oe][PATCH v3 1/1] nodejs: cleanup and update

Hi Martin, On 12/22/15 10:49, Martin Jansa wrote: >> That was what I was trying to do :-) I don't have much experience in >> this, I've been asking on IRC and the mailing lists, and there aren't >> many examples to copy. I think the following works: >> >> COMPATIBLE_MACHINE_armv4 =

Re: [oe] [meta-oe][PATCH v2] nodejs: cleanup and update

On 12/18/15 06:51, Martin Jansa wrote: > On Tue, Dec 01, 2015 at 01:19:25PM -0500, Trevor Woerner wrote: >> Remove old nodejs_0.4.12 and update nodejs_0.12.7 to the latest stable >> nodejs_4.2.2. > It does something strange with CC and ends with invalid parameter for > qemu

[oe] [meta-oe][PATCH v3 1/1] nodejs: cleanup and update

-by: Trevor Woerner <twoer...@gmail.com> --- .../nodejs/nodejs/enable-armv5e-build.patch| 22 -- .../nodejs/nodejs4/libev-cross-cc_0.4.12.patch | 13 -- meta-oe/recipes-devtools/nodejs/nodejs4_0.4.12.bb | 49 -- .../nodejs/{nodejs_0.12.7.bb => nodejs

[oe] [meta-oe][PATCH v3 0/1] nodejs cleanup and update

to successfully run a qemuppc64 VM Changes from v2: handle qemuarm build failure Changes from v1: don't try to keep and unite the old recipe versions, just replace them with the latest stable Trevor Woerner (1): nodejs: cleanup and update .../nodejs/nodejs/enable-armv5e-build.patch

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2015-12-17

On 12/18/15 06:25, Martin Jansa wrote: > === qemuarm (1) === > * /meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs_4.2.2.bb, > do_compile I'm having a look at this one. -- ___ Openembedded-devel mailing list

[oe] [meta-oe][PATCH 1/2] nodejs: cleanup

such that there are two nodejs recipes from which to choose. A user can select between them using the regular PREFERRED_VERSION_nodejs notation. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- .../enable-armv5e-build.patch | 0 .../{nodejs => node

[oe] [meta-oe][PATCH 2/2] nodejs: add recipe for latest stable

The latest stable version of nodejs is 4.2.2; add a recipe to make it available. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- meta-oe/recipes-devtools/nodejs/nodejs_4.2.2.bb | 9 + 1 file changed, 9 insertions(+) create mode 100644 meta-oe/recipes-devtools/nodejs/nodejs

[oe] [meta-oe][PATCH 0/2] nodejs cleanup and add

a new recipe for the latest stable version. Trevor Woerner (2): nodejs: cleanup nodejs: add recipe for latest stable .../enable-armv5e-build.patch | 0 .../{nodejs => nodejs-0.12.7}/no-registry.patch| 0 .../libev-cross-cc_0.4.12.patch| 0 m

Re: [oe] [meta-oe][PATCH 1/2] nodejs: cleanup

On 12/01/15 12:22, Martin Jansa wrote: > As it was already PNBLACKLISTed I wouldn't mind removing it completely and > replacing 0.12.7 with new version (without introducing the .inc) file. Thanks for providing the background info, I was wondering why it was implemented this way. I'll submit a v2

[oe] [meta-oe][PATCH v2] nodejs: cleanup and update

Remove old nodejs_0.4.12 and update nodejs_0.12.7 to the latest stable nodejs_4.2.2. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- .../nodejs/nodejs4/libev-cross-cc_0.4.12.patch | 13 -- meta-oe/recipes-devtools/nodejs/nodejs4_0.4.12.bb | 49 -- .../

Re: [oe] [OE-core] Patchwork & patch handling improvements

On 11/26/15 16:00, Paul Eggleton wrote: > I'm also > trying to ensure that the patch validation is generic enough so it can live > in > OE-Core, and thus we can easily update and refine it over time in line with > the > code itself as well as encourage submitters to use the script on their

Re: [oe] [meta-browser][PATCH 1/3] chromium: Allow to build in Debug mode.

On 09/15/15 08:50, Carlos Alberto Lopez Perez wrote: > * Add also a patch that workarounds a build error when building > in Debug mode and using GCC. This patch has no effect when > building in Release mode because is guarded within ifdef(debug) > blocks. > > Signed-off-by: Carlos

Re: [oe] REMINDER! Fwd: meta-oe and oe-core mirror repos going away at the end of June

Could http://patchwork.openembedded.org/ be also updated? -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] ODROID-C1 support

On 05/21/15 17:18, Khem Raj wrote: On May 21, 2015, at 11:26 AM, Trevor Woerner twoer...@gmail.com wrote: Why would someone include your layer and not build for odroidc1 or wetekplay? Sometimes that's what people do ;-) (look at Angstrom, for example). Besides, a BSP layer should be able

Re: [oe] ODROID-C1 support

Hi Christian, On 05/05/15 11:40, Christian Ege wrote: I've created a BSP Layer for the ODROID-C1 and other Amlogic based devices like the Wetek.Play https://github.com/linux-meson/meta-amlogic Thanks! I've been playing with your layer. For the most part it's going well. I've noticed a small

Re: [oe] [meta-oe][PATCH 01/20] smstools: fix PN - BPN for multilib

On 05/12/15 10:45, Martin Jansa wrote: On Tue, May 12, 2015 at 01:43:19PM +0100, Paul Eggleton wrote: On Monday 11 May 2015 11:27:04 Martin Jansa wrote: On Fri, May 08, 2015 at 03:42:16PM +0800, Yi Zhao wrote: Signed-off-by: Yi Zhao yi.z...@windriver.com Changes 03, 18, 20 didn't make it to

Re: [oe] ODROID-C1 support

Hi Christian, Sorry, I missed your announcement before replying to Armin's post about the -xu3! I was reading through my backlog of Yocto mailing list emails and hadn't made it to my OE backlog yet ;-) I hope we can all pull together some sort of common amlogic/odroid layer(s) together. Best

Re: [oe] Odroid-xu3 support

On 15-05-07 02:56 AM, Christian Ege wrote: From the ODROID family I do only own a ODROID-C1. If there will be a combined Layer for all odroid devices I will port my recipes to this and can help on supporting it. I am mostly interested in Multimedia stuff and I do plan to setup a separate layer

Re: [oe] Odroid-xu3 support

On 05/04/15 23:56, akuster808 wrote: I have added support for the Odroid XU3 board. This layer can be found at https://github.com/akuster/meta-odroid. It supports XFCE graphics and has sdcard image support. Sounds great! In addition to your meta-odroid there are also:

Re: [oe] Odroid-xu3 support

On 05/06/15 16:24, akuster808 wrote: On 05/06/2015 01:17 PM, Trevor Woerner wrote: It'd be nice if someone could put together one meta-odroid that would support them all ;-) Yep. looking into that. That's great to hear :-D Which device(s) do you have, just the -xu3? My -c1 arrived yesterday

Re: [oe] [PATCH] twm: Upgrade to 1.0.8

Perhaps the -M option should have been used here? -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-browser][PATCH] nspr: rename .bbappend to match new version from oe-core

Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- recipes-support/nspr/{nspr_4.10.3.bbappend = nspr_4.10.7.bbappend} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename recipes-support/nspr/{nspr_4.10.3.bbappend = nspr_4.10.7.bbappend} (100%) diff --git a/recipes-support/nspr

Re: [oe] overriding tasks with EXPORT_FUNCTIONS

On 07/14/14 08:26, Paul Eggleton wrote: Unfortunately as far as the BitBake manual is concerned, it pretty much has to be abstract. Remember that there are no base implementations of any task functions in BitBake itself; the ones you refer to are in OE's base.bbclass. In reality there are

Re: [oe] some questions about overriding tasks

Maybe the following email thread will help? http://lists.openembedded.org/pipermail/openembedded-core/2013-October/085319.html -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org

Re: [oe] [meta-oe][MASTER][PATCH] lxdm: add libpam DEPENDS

Hi Steve, On 25 June 2014 00:16, Stephen Arnold stephen.arnol...@gmail.com wrote: Yeah, it would certainly make more sense with a packageconfig option for that; currently it doesn't work either with or without the pam feature due to the missing plugins. So if you want hard deps, then the

[oe] [meta-oe][MASTER][PATCH] lxdm: add libpam DEPENDS

Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-graphics/lxdm/lxdm_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-graphics/lxdm/lxdm_git.bb b/meta-oe/recipes-graphics/lxdm/lxdm_git.bb index dc40fb2..d0eb516 100644 --- a/meta

Re: [oe] [meta-oe][MASTER][PATCH] lxdm: add libpam DEPENDS

On 06/24/14 16:02, Stephen Arnold wrote: but not as hard deps (since pam is an optional feature). I wasn't 100% before sending that patch, but somehow I assumed it'd be best as a: DEPENDS += ${@base_contains(DISTRO_FEATURES, pam... or some such. But I put it as a hard DEPENDS because lxdm has

Re: [oe] Website Text

On 3 May 2014 05:15, Jack Mitchell wrote: The current website address is http://frontpage.openembedded.org/ My feeling is that there is a chance people will be coming to the OE website with a board already in front of them, looking to find out if OE supports it and how they might go about

Re: [oe] Website Text

On 05/06/14 12:12, Paul Eggleton wrote: So I'd hope that the machine listing in the layer index could be made to help with that. Absolutely, for raw recipe information or information on which MACHINEs are supported the layer index would be a good choice. But there's a fair amount of difference

Re: [oe] [OE-core] State of bitbake world, test-dependencies 2014-04-18

Hi Martin, Just to confirm... when we work on this, we should be working against master-next? Best regards, Trevor -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org

Re: [oe] [meta-oe][PATCH 1/3] liblockfile: remove configure warning

On 04/12/14 06:44, Martin Jansa wrote: Can you please rebase on current master (maybe you have one more patch which you haven't sent), because in master there is: EXTRA_OECONF = --enable-shared --enable-static so this doesn't apply. Okay, I'll send a v2. --

[oe] [meta-oe][PATCH 0/2] updates for terminus-font

In order to successfully build terminus-font, the xorg utility bdftopcf needs to be available on the native host. This patch set adds a recipe for bdftopcf then updates terminus-font to add this DEPENDS. Trevor Woerner (2): bdftopcf: add recipe terminus-font: update DEPENDS .../recipes

[oe] [meta-oe][PATCH 2/2] terminus-font: update DEPENDS

This recipe requires the native tool bdftopcf to be available. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-graphics/terminus-font/terminus-font_4.38.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-graphics/terminus-font

[oe] [meta-oe][PATCH 1/2] bdftopcf: add recipe

Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-graphics/xorg-app/bdftopcf_1.0.4.bb | 13 + 1 file changed, 13 insertions(+) create mode 100644 meta-oe/recipes-graphics/xorg-app/bdftopcf_1.0.4.bb diff --git a/meta-oe/recipes-graphics/xorg-app

[oe] [meta-oe][PATCH] acpitests: add individual checksums

This recipe includes two source tarballs, add a second set of checksums so both have checksum definitions. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-extended/acpica/acpitests_20140114.bb | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff

[oe] [meta-oe][PATCH] licenses: add The Open Group Public License

This is the license used for the motif library. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/licenses/OGPL | 104 ++ 1 file changed, 104 insertions(+) create mode 100644 meta-oe/licenses/OGPL diff --git a/meta-oe/licenses

[oe] ignore Re: [meta-oe][PATCH] licenses: add The Open Group Public License

oops, I should specify *OPEN*motif. v2 coming up -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-oe][PATCH v2] licenses: add The Open Group Public License

This is the license used for the openmotif library. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/licenses/OGPL | 104 ++ 1 file changed, 104 insertions(+) create mode 100644 meta-oe/licenses/OGPL diff --git a/meta-oe

[oe] [meta-gpe][PATCH] fbreader: remove old non-working recipe

to retrieve version 0.12.10 from that location fails too. Note that there is a _git version of this recipe which builds just fine. Therefore my recommendation is to simply remove this non-building recipe for a 4+-year-old version of fbreader and keeping the _git version which does build. Trevor

[oe] [meta-gpe][PATCH] fbreader: remove old, non-building version

. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- .../fbreader/fbreader-0.12.10/Makefile.patch | 22 .../fbreader/fbreader-0.12.10/gcc45.patch | 20 --- .../recipes-support/fbreader/fbreader_0.12.10.bb | 42 -- 3 files changed, 84

[oe] [meta-networking][PATCH] sethdlc: remove

/linux/include/linux/hdlc.h:14, from sethdlc.c:19: /usr/src/linux/include/linux/linkage.h:7:25: fatal error: asm/linkage.h: No such file or directory #include asm/linkage.h Trevor Woerner (1): sethdlc: remove .../recipes-connectivity/sethdlc/sethdlc.bb

[oe] [meta-networking][PATCH] sethdlc: remove

Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- .../recipes-connectivity/sethdlc/sethdlc.bb| 30 -- 1 file changed, 30 deletions(-) delete mode 100644 meta-networking/recipes-connectivity/sethdlc/sethdlc.bb diff --git a/meta-networking/recipes

[oe] [meta-gnome][PATCH] abiword: force build order

There is a race condition whereby libgoffice.la must be built (and exist) before the rest of the code in src is built. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-gnome/recipes-gnome/abiword/abiword_3.0.0.bb | 8 1 file changed, 8 insertions(+) diff --git a/meta

[oe] [meta-gnome][PATCH] abiword: force build order

}, but it still failed. Trevor Woerner (1): abiword: force build order meta-gnome/recipes-gnome/abiword/abiword_3.0.0.bb | 8 1 file changed, 8 insertions(+) -- 1.9.0 -- ___ Openembedded-devel mailing list Openembedded-devel

[oe] [meta-multimedia][PATCH] libdc1394 SOBBW patch

Here is a patch for a build issue discovered while doing a world build. Trevor Woerner (1): libdc1394: disable building examples meta-multimedia/recipes-multimedia/libdc1394/libdc1394_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 1.9.0

[oe] [meta-multimedia][PATCH] libdc1394: disable building examples

format not recognized Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-multimedia/recipes-multimedia/libdc1394/libdc1394_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-multimedia/recipes-multimedia/libdc1394/libdc1394_git.bb b/meta-multimedia

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2014-04-03

Is anyone seeing any build failures with proj-4.8.0? Or does anyone have any local fixes? This one has been failing for me for a while, and yet doesn't show up on the SOBBW lists. -- ___ Openembedded-devel mailing list

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2014-04-03

On 04/03/14 09:06, Martin Jansa wrote: Other recipes are still free for fixing, please fix them and send reply to this thread when you start looking into it, so that nobody duplicates work. I'm going to be looking at some of the qa.log warnings over the weekend. --

[oe] [meta-xfce][PATCH] xfconf: remove unrecognized configure option

This option was causing a QA warning: NOTE: QA Issue: xfconf: configure was passed unrecognised options: --with-sysroot Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-xfce/recipes-xfce/xfconf/xfconf_4.10.0.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/meta-xfce

[oe] [meta-oe][PATCH 0/3] liblockfile updates for SOBBW

This series implements a bunch of fixups to remove QA configure warnings. The first patch gets rid of a warning which is logged, the remaining patches get rid of warnings which are suppressed. Trevor Woerner (3): liblockfile: remove configure warning liblockfile: remove dependency tracking

[oe] [meta-oe][PATCH 2/3] liblockfile: remove dependency tracking option

--disable-dependency-tracking is only available where automake is used. liblockfile doesn't use automake, therefore remove this option to avoid a configure warning. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-extended/liblockfile/liblockfile_1.09.bb | 1 + 1 file

[oe] [meta-oe][PATCH 1/3] liblockfile: remove configure warning

This fix gets rid of the following warning: configure: WARNING: unrecognized options: ... --with-libtool-sysroot Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- .../liblockfile/liblockfile-1.09/configure.patch | 18 ++ .../recipes-extended/liblockfile

[oe] [meta-oe][PATCH] asio: package bump

This recipe had been failing to build, bumping to the latest stable release resolves all build issues. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-support/asio/asio.inc | 11 ++- meta-oe/recipes-support/asio/asio_1.10.1.bb | 6 ++ meta-oe

[oe] 'asio' fix for SOBBW (2014-03-29)

Hi Martin, Here is a fix for your State of bitbake world, Failed tasks 2014-03-29. Best regards, Trevor Trevor Woerner (1): asio: package bump meta-oe/recipes-support/asio/asio.inc | 11 ++- meta-oe/recipes-support/asio/asio_1.10.1.bb | 6 ++ meta-oe/recipes-support

[oe] [meta-oe][PATCH 0/4] 'gtkmathview' fix for SOBBW (2014-03-29)

Hi Martin, Here is a fix for your State of bitbake world, Failed tasks 2014-03-29. This patch set provides fixes and some clean-up for the gtkmathview package. Best regards, Trevor Trevor Woerner (4): gtkmathview: fix B!=S gtkmathview: fix qa issue gtkmathview: fix build error

[oe] [meta-oe][PATCH 3/4] gtkmathview: fix build error

[-fpermissive] Upstream-Status: Submitted [padovani .at. di .dot. unito .dot. it] Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- .../mml-widget/gtkmathview/qualify-lookup.diff | 13 + meta-oe/recipes-extended/mml-widget/gtkmathview_0.8.0.bb| 1 + 2 files

[oe] [meta-oe][PATCH 1/4] gtkmathview: fix B!=S

This package does not support building out of a separate directory from the source. Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-extended/mml-widget/gtkmathview_0.8.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-extended

[oe] [meta-oe][PATCH 2/4] gtkmathview: fix qa issue

configure was passed unrecognised options: --disable-binreloc Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-extended/mml-widget/gtkmathview_0.8.0.bb | 2 -- 1 file changed, 2 deletions(-) diff --git a/meta-oe/recipes-extended/mml-widget/gtkmathview_0.8.0.bb b/meta

[oe] [meta-oe][PATCH 4/4] gtkmathview: run through oe-stylize.py

Signed-off-by: Trevor Woerner trevor.woer...@linaro.org --- meta-oe/recipes-extended/mml-widget/gtkmathview_0.8.0.bb | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/meta-oe/recipes-extended/mml-widget/gtkmathview_0.8.0.bb b/meta-oe/recipes-extended/mml-widget

<    1   2   3   4   >