Re: [oe] [meta-oe][PATCH] CANopenNode: recipe for building the CANopenSocket tools

Thanks for your feedback! I have updated it to use gitsm. On Wed, Jul 13, 2016 at 9:50 AM, Derek Straka wrote: > Have you tried using the gitsm ( > > https://www.yoctoproject.org/docs/2.1/bitbake-user-manual/bitbake-user-manual.html#gitsm-fetcher > ) > fetcher instead of git?

Re: [oe] [meta-oe][PATCH] CANopenNode: recipe for building the CANopenSocket tools

On Wed, Jul 13, 2016 at 8:00 AM, Gary Thomas wrote: > On 2016-07-13 16:57, cynthiachiu wrote: > >> Initial check-in for the CANopenSocket tools recipe. >> >> Signed-off-by: cynthiachiu >> --- >> .../canopennode/canopensocket_git.bb |

Re: [oe] [meta-oe][PATCH] CANopenNode: recipe for building the CANopenSocket tools

Have you tried using the gitsm ( https://www.yoctoproject.org/docs/2.1/bitbake-user-manual/bitbake-user-manual.html#gitsm-fetcher) fetcher instead of git? I believe gitsm should do all of the submodule init and update actions automatically rather than having to use a do_compile_prepend. -Derek

[oe] [meta-oe][PATCH] zeromq: Update to version 4.1.5.

Added PACKAGECONFIG to use libsodium instead of builtin tweetnacl. Compiling with current master led to: | ../zeromq-4.1.5/src/ctx.cpp:50:28: fatal error: randombytes.h: No such file or directory | # include "randombytes.h" | ^ | compilation terminated. |

Re: [oe] [meta-oe][PATCH] libsodium: Update to 1.0.10.

On Wed, Jul 13, 2016 at 6:28 AM, Philip Balister wrote: > Signed-off-by: Philip Balister > --- > meta-oe/recipes-support/libsodium/libsodium_1.0.10.bb | 10 ++ > meta-oe/recipes-support/libsodium/libsodium_1.0.8.bb | 11 --- > 2 files

[oe] [meta-oe][PATCHv2] libsodium: Update to 1.0.10.

The LICENSE file checksum changed due to copyright year update. See: https://github.com/jedisct1/libsodium/commit/78d07701229d94ce48c74048f47e378937582ba5#diff-9879d6db96fd29134fc802214163b95a Signed-off-by: Philip Balister ---

Re: [oe] [meta-oe][PATCH] libsodium: Update to 1.0.10.

On 07/13/2016 01:53 PM, Khem Raj wrote: > On Wed, Jul 13, 2016 at 6:28 AM, Philip Balister wrote: >> Signed-off-by: Philip Balister >> --- >> meta-oe/recipes-support/libsodium/libsodium_1.0.10.bb | 10 ++ >>

Re: [oe] [meta-oe][PATCHv2] libsodium: Update to 1.0.10.

OK send a v2 with this info in commit header On Wed, Jul 13, 2016 at 11:42 AM, Philip Balister wrote: > The LICENSE file checksum changed due to copyright year update. See: >

Re: [oe] [meta-oe][PATCH] plymouth: remove virtual prefix for RPROVIDES

Infact it is a direct replacement On Jul 13, 2016 3:32 PM, "Paul Eggleton" wrote: > On Tue, 12 Jul 2016 15:58:45 Martin Jansa wrote: > > On Fri, Jul 08, 2016 at 12:30:52PM -0400, Joe MacDonald wrote: > > > The 'virtual' namespace is only intended to be used for

Re: [oe] [meta-oe][PATCH] plymouth: remove virtual prefix for RPROVIDES

On Tue, 12 Jul 2016 15:58:45 Martin Jansa wrote: > On Fri, Jul 08, 2016 at 12:30:52PM -0400, Joe MacDonald wrote: > > The 'virtual' namespace is only intended to be used for build-time > > dependencies, not in the runtime package namespace. > > > > Signed-off-by: Joe MacDonald

Re: [oe] [RFC][PATCH] mozjs: add 45.0.2

Op 12-07-16 om 12:05 schreef Koen Kooi: > Mozjs 17 has serious issues on non-x86 64 bit hardware and worse, on 48/51 > bit VA architectures. The systemd -> polkit -> mozjs chain renders various > armv8 systems unbootable due to that. There are no fixes for mozjs17, only > more recent versions.

Re: [oe] [meta-networking][PATCH] augeas: Move from oe-core

On 12 July 2016 at 16:41, Joe MacDonald wrote: > [[oe] [meta-networking][PATCH] augeas: Move from oe-core] On 16.07.12 (Tue > 14:50) Jussi Kukkonen wrote: > > > augeas is being removed from oe-core as nothing there uses or tests > > it. Move the recipe to

[oe] nodejs: newer npm?

The current (at least 4.4.4) nodejs recipe also creates nodejs-npm which is npm version 2.15.1. I'm trying to run angularjs that needs npm >= 3.3.x. I've not yet tried the update to 4.4.5, so if this fixes the issue just let me know. What needs to be done to get a newer npm? BTW, the current

Re: [oe] nodejs: newer npm?

On 2016-07-13 09:39, Gary Thomas wrote: The current (at least 4.4.4) nodejs recipe also creates nodejs-npm which is npm version 2.15.1. I'm trying to run angularjs that needs npm >= 3.3.x. I've not yet tried the update to 4.4.5, so if this fixes the issue just let me know. What needs to be

[oe] [meta-webserver][PATCH] apache2: update to version 2.4.23

Signed-off-by: Derek Straka --- .../apache2/{apache2-native_2.4.20.bb => apache2-native_2.4.23.bb}| 4 ++-- .../recipes-httpd/apache2/{apache2_2.4.20.bb => apache2_2.4.23.bb}| 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) rename

Re: [oe] nodejs: newer npm?

I am currently using angular from a different meta layer. https://github.com/imyller/meta-nodejs It maintains newer versions of nodejs. It might be something you want to try. On Wednesday, July 13, 2016 10:11:05 AM Gary Thomas wrote: > On 2016-07-13 09:39, Gary Thomas wrote: > > The current

[oe] [meta-oe][PATCH] libsodium: Update to 1.0.10.

Signed-off-by: Philip Balister --- meta-oe/recipes-support/libsodium/libsodium_1.0.10.bb | 10 ++ meta-oe/recipes-support/libsodium/libsodium_1.0.8.bb | 11 --- 2 files changed, 10 insertions(+), 11 deletions(-) create mode 100644

[oe] [meta-oe][PATCH] CANopenNode: recipe for building the CANopenSocket tools

Initial check-in for the CANopenSocket tools recipe. Signed-off-by: cynthiachiu --- .../canopennode/canopensocket_git.bb | 31 ++ 1 file changed, 31 insertions(+) create mode 100644

Re: [oe] [meta-oe][PATCH] CANopenNode: recipe for building the CANopenSocket tools

On 2016-07-13 16:57, cynthiachiu wrote: Initial check-in for the CANopenSocket tools recipe. Signed-off-by: cynthiachiu --- .../canopennode/canopensocket_git.bb | 31 ++ 1 file changed, 31 insertions(+) create mode 100644

Re: [oe] nodejs: newer npm?

On 2016-07-13 16:41, Davis, Michael wrote: I am building for intel core2-32 with an nginx backend. I believe the layer exists to keep packages more closely aligned with the upstream project. I personally use it for the current 6.x releases of nodejs. Fair enough (although I believe that this

Re: [oe] nodejs: newer npm?

On 2016-07-13 15:29, Davis, Michael wrote: I am currently using angular from a different meta layer. https://github.com/imyller/meta-nodejs It maintains newer versions of nodejs. It might be something you want to try. I have tried this and yes, the versions are newer, but my simple example

Re: [oe] nodejs: newer npm?

I am building for intel core2-32 with an nginx backend. I believe the layer exists to keep packages more closely aligned with the upstream project. I personally use it for the current 6.x releases of nodejs. On Wednesday, July 13, 2016 04:24:52 PM Gary Thomas wrote: > On 2016-07-13 15:29,