Re: [yocto] Python 3 internal package dependencies

2017-06-08 Thread Burton, Ross
On 8 June 2017 at 07:47, Craig McQueen  wrote:

> Is it worth trying to improve the internal package RDEPENDS in the Python
> 3 recipe, or is it better for recipes for Python apps to just manually list
> all the sub-dependencies as needed?
>

Definitely worth improving the internal dependencies, they're generated by
the scripts in oe-core/scripts/contrib/python.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

2017-06-08 Thread Andrei Gherzan
On Thu, Jun 8, 2017 at 5:22 AM, Khem Raj  wrote:

> On Wed, Jun 7, 2017 at 9:09 PM, Petter Mabäcker  wrote:
> > 2017-06-08 00:54 skrev Khem Raj:
> >
> >
> > On Wed, Jun 7, 2017 at 2:17 PM Petter Mabäcker 
> wrote:
> >>
> >> Update to latest available revision, in order to include proper rpi3
> >> support as well as latest fixes.
> >>
> >> Signed-off-by: Petter Mabäcker 
> >> ---
> >>  .../files/remove-initscript-lsb-dependency.patch   | 37
> >> --
> >>  recipes-devtools/pi-blaster/pi-blaster.inc |  2 +-
> >>  recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
> >>  3 files changed, 30 insertions(+), 11 deletions(-)
> >>
> >> diff --git
> >> a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-
> dependency.patch
> >> b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-
> dependency.patch
> >> index 7ea9a3b..c8afe60 100644
> >> ---
> >> a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-
> dependency.patch
> >> +++
> >> b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-
> dependency.patch
> >> @@ -1,13 +1,28 @@
> >> -Remove dependencies on LSB functions
> >> +From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
> >> +From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
> >> +Date: Sun, 4 Jun 2017 12:22:40 +0200
> >> +Subject: [PATCH] Remove dependencies on LSB functions
> >> +MIME-Version: 1.0
> >> +Content-Type: text/plain; charset=UTF-8
> >> +Content-Transfer-Encoding: 8bit
> >> +
> >> +See this as a rebase of the previous 'Remove dependencies on LSB
> >> +functions patch' with only minor modifications from the original
> version,
> >> +based on the work done by Alex Lennon 
> in
> >> +'25fd817 pi-blaster: Added recipe'.
> >>
> >>  Upstream-Status: Inappropriate [configuration]
> >>
> >> -Signed-off-by: Alex Lennon 
> >> +Signed-off-by: Petter Mabäcker 
> >> +---
> >> + debian/pi-blaster.init | 38 +++---
> >> + 1 file changed, 7 insertions(+), 31 deletions(-)
> >>
> >> -diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
> >>  git.org/pi-blaster.boot.sh 2014-05-20 14:49:44.378582168 +0100
> >> -+++ git/pi-blaster.boot.sh 2014-05-20 14:51:08.330582386 +0100
> >> -@@ -28,12 +28,12 @@
> >> +diff --git a/debian/pi-blaster.init b/debian/pi-blaster.init
> >> +index b142d70..01a686c 100644
> >> +--- a/debian/pi-blaster.init
> >>  b/debian/pi-blaster.init
> >> +@@ -28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
> >>   [ -r /etc/default/$NAME ] && . /etc/default/$NAME
> >>
> >>   # Load the VERBOSE setting and other rcS variables
> >> @@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh
> >> git/pi-blaster.boot.sh
> >>
> >>   #
> >>   # Function that starts the daemon/service
> >> -@@ -77,48 +77,23 @@
> >> +@@ -77,48 +77,24 @@ do_stop()
> >>
> >>   case "$1" in
> >> start)
> >> @@ -52,6 +67,7 @@ diff -ur git.org/pi-blaster.boot.sh
> >> git/pi-blaster.boot.sh
> >> # 'force-reload' alias
> >> #
> >>  -  log_daemon_msg "Restarting $DESC" "$NAME"
> >> ++  echo "Restarting $DESC" "$NAME"
> >> do_stop
> >>  -  case "$?" in
> >>  -0|1)
> >> @@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh
> >> git/pi-blaster.boot.sh
> >>  -  log_end_msg 1
> >>  -  ;;
> >>  -  esac
> >> -+  do_start
> >> ++do_start
> >> ;;
> >> *)
> >>  -  echo "Usage: $SCRIPTNAME {start|stop|status|restart|
> force-reload}"
> >> >&2
> >> -+  echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
> >> ++  echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
> >> exit 3
> >> ;;
> >>   esac
> >> +--
> >> +1.9.1
> >> +
> >> diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc
> >> b/recipes-devtools/pi-blaster/pi-blaster.inc
> >> index a3beccc..a548957 100644
> >> --- a/recipes-devtools/pi-blaster/pi-blaster.inc
> >> +++ b/recipes-devtools/pi-blaster/pi-blaster.inc
> >> @@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins
> >> you request of a Raspbe
> >>  HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
> >>  SECTION = "devel/libs"
> >>  LICENSE = "MIT"
> >> -LIC_FILES_CHKSUM =
> >> "file://README.md;beginline=157;endline=170;md5=
> f20832f31126609af5a7bf2340014540"
> >> +LIC_FILES_CHKSUM =
> >> "file://README.md;beginline=212;endline=239;md5=
> a012868ef5f83b9f257af253d7cb07a3"
> >
> >
> > What changed here ?
> >
> > The license is added in the end of the README.md so in this case some
> > additional description + modifications earlier in the README.md caused
> the
> > license text to move place. When it comes to the license text I could
> only
> > find changes in whitespace and newlines. They seems to have been caused
> by
> > the pi-blaster commit: '0e1a1df Cleaning up the README'
> >
> > BR Petter
> >
> > $ diff -Naur ec5e1b4c.README.md README.md | tail -n 38
> >
>
> perfect add few lines to the commit message about this


That would be nice.
-- 

Re: [yocto] [PATCH] qt4-native: depend on icu-native to fix build on systems with icu >=59

2017-06-08 Thread Alexander Kanavin

On 06/07/2017 06:47 PM, Cody P Schafer wrote:

Yep, for `master` that is certainly true.

For `morty` & `pyro` though, meta-qt4 could keep working by using icu-native.

The source of this issue being qt4's general incompatibility with C++
11 (we build with c++98 because of build errors with the newer std)
makes me wonder if it will even be possible to continue supporting qt4
going forward.

This may turn out like the openssl conflicts in that we'll need to
disable qt4's use of icu entirely.


I should give you a heads up: we (the yocto project) are going to remove 
qt4 builds from the autobuilder altogether, sometime during this cycle. 
The repo will stay, and patches will be accepted though.


So it's up to you to solve these issues, but I wouldn't want to take
patches that fix up older releases, while the master branch remains 
broken. We have a 'master first' policy :)


Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Python 3 internal package dependencies

2017-06-08 Thread Alexander Kanavin

On 06/08/2017 11:50 AM, Burton, Ross wrote:


Is it worth trying to improve the internal package RDEPENDS in the
Python 3 recipe, or is it better for recipes for Python apps to just
manually list all the sub-dependencies as needed?


Definitely worth improving the internal dependencies, they're generated
by the scripts in oe-core/scripts/contrib/python.


I'll bite: should we just drop the the splitting of Python modules into 
their own packages? In 2017, this is more trouble than it's worth, IMO.



Alex

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] What's up with python3

2017-06-08 Thread Alexander Kanavin

On 06/08/2017 10:28 AM, Gary Thomas wrote:

I'm building using Poky/Yocto master
576821ea0a7558b626ccc87e9ae0e9ee40864956
and I've noticed that python3 (target) is being built for my image, but it
doesn't end up in the actual image.  None of my own recipes mention python3
at all, yet virtually every recipe that's used in the build depend on it.

I've listed all the recipes used in my build (from bitbake -g =>
recipe-depends.dot)
and sucked out the ones that claim to depend on python3.  I don't see
why, for
example, python(2) depends on python3?

Can someone explain this?  I've added the appropriate files to this email.

I'm mostly curious, but also a bit concerned that my builds are doing more
than they need (and hence just taking longer than they might need to)


Typically for two reasons:

a) a recipe needs to execute python during build, and host python is not 
suitable for some reason - so native python is built and used;


b) a supplementary package needs python, while the main package does not 
- most often this is the -ptest package, which will not end up in the 
image, unless you ask.


Alex

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Python 3 internal package dependencies

2017-06-08 Thread Burton, Ross
On 8 June 2017 at 12:02, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:

> I'll bite: should we just drop the the splitting of Python modules into
> their own packages? In 2017, this is more trouble than it's worth, IMO.
>

Hard to say without data.  How big is the entire module set?  What
percentage of that goes into e.g. core-image-sato if the dependencies are
fixed so python3-modules doesn't get installed?  Are there just a few
modules that are large and a more maintainable split would be
minimal/everything (as Debian does, I believe)?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] What's up with python3

2017-06-08 Thread Gary Thomas

On 2017-06-08 13:09, Alexander Kanavin wrote:

On 06/08/2017 10:28 AM, Gary Thomas wrote:

I'm building using Poky/Yocto master
576821ea0a7558b626ccc87e9ae0e9ee40864956
and I've noticed that python3 (target) is being built for my image, but it
doesn't end up in the actual image.  None of my own recipes mention python3
at all, yet virtually every recipe that's used in the build depend on it.

I've listed all the recipes used in my build (from bitbake -g =>
recipe-depends.dot)
and sucked out the ones that claim to depend on python3.  I don't see
why, for
example, python(2) depends on python3?

Can someone explain this?  I've added the appropriate files to this email.

I'm mostly curious, but also a bit concerned that my builds are doing more
than they need (and hence just taking longer than they might need to)


Typically for two reasons:

a) a recipe needs to execute python during build, and host python is not suitable for some reason - so native python is 
built and used;


Not that: I filtered out all uses of python3-native - these are only *target* 
dependencies



b) a supplementary package needs python, while the main package does not - most often this is the -ptest package, which 
will not end up in the image, unless you ask.


None of my recipes build -ptest stuff:
  $ find tmp/deploy/ipk/ -name "*ptest*"

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] What's up with python3

2017-06-08 Thread Burton, Ross
On 8 June 2017 at 08:28, Gary Thomas  wrote:

> I've listed all the recipes used in my build (from bitbake -g =>
> recipe-depends.dot)
> and sucked out the ones that claim to depend on python3.  I don't see why,
> for
> example, python(2) depends on python3?
>

I'm 90% sure that this all comes through opkg-utils being the provider for
update-alternatives.

You could verify this by disabling the python PACKAGECONFIG in opkg-utils.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-cgl][PATCH] poky-cgl: avoid installing multiple syslogs

2017-06-08 Thread Adrian Dudau
On fre, 2017-06-02 at 15:59 +0800, jackie.hu...@windriver.com wrote:
> From: Jackie Huang 
> 
> do_rootfs fails if multiple syslogs are installed:
> > 
> > Error: package syslog-ng-3.8.1-r0.i586 conflicts with sysklogd
> > provided
>   by sysklogd-1.5.1-r0.i586
> 
> core-image-cgl requires packagegroup-core-full-cmdline which depends
> on VIRTUAL-RUNTIME_syslog (default to sysklogd), so set the
> VIRTUAL-RUNTIME_syslog in distro conf and no need to depends
> on any syslog in packagegroup-cgl-applications, then we ensure
> that only one syslog is installed to avoid conflicts.
> 
> Signed-off-by: Jackie Huang 
> ---
>  meta-cgl-common/conf/distro/poky-cgl.conf  | 4
> 
>  meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb | 2
> --
>  2 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-cgl-common/conf/distro/poky-cgl.conf b/meta-cgl-
> common/conf/distro/poky-cgl.conf
> index 90cc82b..69f6200 100644
> --- a/meta-cgl-common/conf/distro/poky-cgl.conf
> +++ b/meta-cgl-common/conf/distro/poky-cgl.conf
> @@ -5,3 +5,7 @@ DISTRO = "poky-cgl"
>  
>  IMAGE_CLASSES += "image_types_uboot"
>  PREFERRED_PROVIDER_virtual/refpolicy="refpolicy-targeted"
> +
> +# we want to use rsyslog as the default syslog, but it's GPLv3, so
> need this
> +# check to switch to syslog-ng if GLPv3 is blacklisted.
> +VIRTUAL-RUNTIME_syslog ?= "${@bb.utils.contains('INCOMPATIBLE_LICENS
> E', 'GPLv3', 'syslog-ng', 'rsyslog', d)}"
> diff --git a/meta-cgl-common/packagegroups/packagegroup-cgl-
> applications.bb b/meta-cgl-common/packagegroups/packagegroup-cgl-
> applications.bb
> index b566e2d..be36075 100644
> --- a/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb
> +++ b/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb
> @@ -40,7 +40,6 @@ RDEPENDS_${PN} = " \
>  quota \
>  smartmontools \
>  monit \
> -syslog-ng \
>  ocfs2-tools \
>  logcheck \
>  samhain-client \
> @@ -48,7 +47,6 @@ RDEPENDS_${PN} = " \
>  audit \
>  pam-passwdqc \
>  libpam \
> -rsyslog \
>  makedumpfile \
>  "
>  
> -- 
> 2.11.0
> 

Patch   good but doesn't apply. Please rebase on origin/master and send
again.

best regards
--Adrian
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Changing terminal font in sato

2017-06-08 Thread Jussi Kukkonen
On 1 June 2017 at 18:58, Gary Thomas  wrote:
>
> How does one change the terminal font (size) used by matchbox-terminal
> in the sato desktop?  I tried the 'matchbox-appearance' app and it didn't
> have any affect, nor could I see a way to change the font.


Hi, sorry for late answer,

matchbox-terminal is a _very_ thin app based on VteTerminal widget:
Modifying Vte font is a single API call but that is not exposed in the app
(as it has no configuration at all). In the short term your options are to
use another more serious terminal or send patches for mb-terminal...

Jussi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] What's up with python3

2017-06-08 Thread Gary Thomas

On 2017-06-08 13:52, Burton, Ross wrote:


On 8 June 2017 at 08:28, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

I've listed all the recipes used in my build (from bitbake -g => 
recipe-depends.dot)
and sucked out the ones that claim to depend on python3.  I don't see why, 
for
example, python(2) depends on python3?


I'm 90% sure that this all comes through opkg-utils being the provider for 
update-alternatives.

You could verify this by disabling the python PACKAGECONFIG in opkg-utils.


I'm impressed!  That eliminated all of them :-)

What would I lose by do this, in general, as it's pretty obvious
that python3 is not needed by any of the recipes I use?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Changing terminal font in sato

2017-06-08 Thread Gary Thomas

On 2017-06-08 14:05, Jussi Kukkonen wrote:

On 1 June 2017 at 18:58, Gary Thomas mailto:g...@mlbassoc.com>> wrote:
 >
 > How does one change the terminal font (size) used by matchbox-terminal
 > in the sato desktop?  I tried the 'matchbox-appearance' app and it didn't
 > have any affect, nor could I see a way to change the font.


Hi, sorry for late answer,

matchbox-terminal is a _very_ thin app based on VteTerminal widget: Modifying Vte font is a single API call but that is 
not exposed in the app (as it has no configuration at all). In the short term your options are to use another more 
serious terminal or send patches for mb-terminal...


OK, thanks.  Any recommendations for an alternative, other than
'xterm' (whose "main.c" has said "Warning!  there be dragons here!"
for more than 20 years :-)

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Changing terminal font in sato

2017-06-08 Thread Burton, Ross
On 8 June 2017 at 13:05, Jussi Kukkonen  wrote:

> matchbox-terminal is a _very_ thin app based on VteTerminal widget:
> Modifying Vte font is a single API call but that is not exposed in the app
> (as it has no configuration at all). In the short term your options are to
> use another more serious terminal or send patches for mb-terminal...
>

There's another alternative: I believe Vte defaults to "Mono", which is an
alias.  Configure fontconfig to pick a different font for the alias.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] What's up with python3

2017-06-08 Thread Burton, Ross
On 8 June 2017 at 13:10, Gary Thomas  wrote:

> What would I lose by do this, in general, as it's pretty obvious
> that python3 is not needed by any of the recipes I use?
>

It's the scripts in opkg-utils, so if you're not installing that in your
image then you won't notice at all.

(looks like the recipe should respect the python PACKAGECONFIG and delete
the python scripts so they can't get packaged)

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] dllmap config for a Mono app

2017-06-08 Thread Joshua Watt
On Thu, 2017-06-08 at 16:41 +1000, Craig McQueen wrote:
> I have a Mono app that uses DllImport to load some functions from
> libraries. The app can't find the libraries unless I create a Mono
> config file containing dllmap lines to map the library's plain "DLL"
> name (e.g. "foo") to the real name of the .so file (e.g.
> "libfoo.so.4").

I'm not familiar with Mono, is libfoo a plain old library that anyone
can use, or it is some special "Mono Library"

> 
> * What would be a good way in the .bb recipe to automatically create
> the required Mono config file? It would need to find the "real" names
> of the library files from the library(s) build output. So it would
> DEPENDS on the library(s).
> 
> * Is it better to create a local config file, or write it into
> /etc/mono/config? (My Mono app has the DllImports in a compiled DLL,
> and so far I've found that I need to create a local MyDll.dll.config
> file; making a MyApp.exe.config file doesn't work.)

Packaging rules require that every file belong to one and only one
package. If your application writes /etc/mono/config, you wouldn't be
able to write that file from any other package, including some other
Mono application. The MyApp.exe.config file (unfortunately) sounds like
the ideal solution, because you know that no other package is going to
try and write that file. Writing MyDll.dll.config runs into the same
problem as /etc/mono/config (at least if you are trying to write it
from your MyApp recipe), as another app might want to write the same
file because it uses the same library but that isn't allowed by the
packaging rules. If you want to write MyDll.dll.config, it should be
done in the recipe that actually creates the dll.

> 



> -- 
> Craig McQueen

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH] qt4-native: depend on icu-native to fix build on systems with icu >=59

2017-06-08 Thread Cody P Schafer
> I should give you a heads up: we (the yocto project) are going to remove qt4
> builds from the autobuilder altogether, sometime during this cycle. The repo
> will stay, and patches will be accepted though.

Thanks for the heads up.

> So it's up to you to solve these issues, but I wouldn't want to take
> patches that fix up older releases, while the master branch remains broken.
> We have a 'master first' policy :)

master first makes sense if master is going to be supported going
forward, but given the extremely stale state of qt4, I don't expect
we'll be able to keep it working (at least as a complete unit) for
very much longer. And we probably shouldn't :) . At some point there
is going to be a last release that works with qt4, forever.

Would it be reasonable to disable icu usage in meta-qt4 master while
switching pyro & morty to using the icu-native package?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH] qt4-native: depend on icu-native to fix build on systems with icu >=59

2017-06-08 Thread Alexander Kanavin

On 06/08/2017 05:22 PM, Cody P Schafer wrote:

Would it be reasonable to disable icu usage in meta-qt4 master while
switching pyro & morty to using the icu-native package?


Yes, absolutely.

Alex

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-cgl][PATCH 0/4] resource-agents: update to 4.0.1 and several fixes

2017-06-08 Thread Adrian Dudau
On fre, 2017-06-02 at 16:21 +0800, jackie.hu...@windriver.com wrote:
> From: Jackie Huang 
> 
> --
> The following changes since commit
> c0afa706e9cdb650c0e8bb79f503743632350b00:
> 
>   core-image-cgl: Remove ROOTFS_PKGMANAGE_BOOTSTRAP (2017-05-24
> 14:19:13 +0200)
> 
> are available in the git repository at:
> 
>   https://github.com/jackiehjm/meta-cgl.git jhuang0/up_resource-
> agents_170602_0
>   https://github.com//tree/jhuang0/up_resource-agents_170602_0
> 
> Jackie Huang (4):
>   resource-agents: fix dependencies
>   resource-agents: fix install-sh not found
>   resource-agents: fix builds error when S != B
>   resource-agents: update to version 4.0.1
> 
>  .../resource-agents/fix-install-sh-not-found.patch | 60
> ++
>  ...uilds-when-srcdir-and-builddir-are-sepera.patch | 39
> ++
>  ...ce-agents_3.9.7.bb => resource-agents_4.0.1.bb} | 20 ++--
>  3 files changed, 115 insertions(+), 4 deletions(-)
>  create mode 100644 meta-cgl-common/recipes-cgl/cluster-resource-
> agents/resource-agents/fix-install-sh-not-found.patch
>  create mode 100644 meta-cgl-common/recipes-cgl/cluster-resource-
> agents/resource-agents/fs.sh-fix-builds-when-srcdir-and-builddir-are-
> sepera.patch
>  rename meta-cgl-common/recipes-cgl/cluster-resource-
> agents/{resource-agents_3.9.7.bb => resource-agents_4.0.1.bb} (82%)
> 
> -- 
> 2.11.0
> 

Same here, patchset is ok but you need to rebase on top of master
latest.

Best regards,
--Adrian
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

2017-06-08 Thread Petter Mabäcker
 

2017-06-08 11:53 skrev Andrei Gherzan: 

> On Thu, Jun 8, 2017 at
5:22 AM, Khem Raj  wrote:
> 
>> On Wed, Jun 7, 2017
at 9:09 PM, Petter Mabäcker  wrote:
>> > 2017-06-08
00:54 skrev Khem Raj:
>> >
>> >
>> > On Wed, Jun 7, 2017 at 2:17 PM
Petter Mabäcker  wrote:
>> >>
>> >> Update to latest
available revision, in order to include proper rpi3
>> >> support as
well as latest fixes.
>> >>
>> >> Signed-off-by: Petter Mabäcker

>> >> ---
>> >>
.../files/remove-initscript-lsb-dependency.patch | 37
>> >>
--
>> >> recipes-devtools/pi-blaster/pi-blaster.inc
| 2 +-
>> >> recipes-devtools/pi-blaster/pi-blaster_git.bb [1] | 2 +-
>>
>> 3 files changed, 30 insertions(+), 11 deletions(-)
>> >>
>> >> diff
--git
>> >>
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>>
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>> index 7ea9a3b..c8afe60 100644
>> >> ---
>> >>
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>> +++
>> >>
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>> @@ -1,13 +1,28 @@
>> >> -Remove dependencies on LSB functions
>> >>
+From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00
2001
>> >> +From: =?UTF-8?q?Petter=20Mab=C3=A4cker?=

>> >> +Date: Sun, 4 Jun 2017 12:22:40 +0200
>> >>
+Subject: [PATCH] Remove dependencies on LSB functions
>> >>
+MIME-Version: 1.0
>> >> +Content-Type: text/plain; charset=UTF-8
>> >>
+Content-Transfer-Encoding: 8bit
>> >> +
>> >> +See this as a rebase of
the previous 'Remove dependencies on LSB
>> >> +functions patch' with
only minor modifications from the original version,
>> >> +based on the
work done by Alex Lennon  in
>> >>
+'25fd817 pi-blaster: Added recipe'.
>> >>
>> >> Upstream-Status:
Inappropriate [configuration]
>> >>
>> >> -Signed-off-by: Alex Lennon

>> >> +Signed-off-by: Petter Mabäcker

>> >> +---
>> >> + debian/pi-blaster.init | 38
+++---
>> >> + 1 file changed, 7
insertions(+), 31 deletions(-)
>> >>
>> >> -diff -ur
git.org/pi-blaster.boot.sh [2] git/pi-blaster.boot.sh [3]
>> >> 
git.org/pi-blaster.boot.sh [2] 2014-05-20 14:49:44.378582168 +0100
>> >>
-+++ git/pi-blaster.boot.sh [3] 2014-05-20 14:51:08.330582386 +0100
>>
>> -@@ -28,12 +28,12 @@
>> >> +diff --git a/debian/pi-blaster.init
b/debian/pi-blaster.init
>> >> +index b142d70..01a686c 100644
>> >> +---
a/debian/pi-blaster.init
>> >>  b/debian/pi-blaster.init
>> >> +@@
-28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
>> >> [ -r
/etc/default/$NAME ] && . /etc/default/$NAME
>> >>
>> >> # Load the
VERBOSE setting and other rcS variables
>> >> @@ -22,7 +37,7 @@ diff -ur
git.org/pi-blaster.boot.sh [2]
>> >> git/pi-blaster.boot.sh [3]
>> >>
>>
>> #
>> >> # Function that starts the daemon/service
>> >> -@@ -77,48
+77,23 @@
>> >> +@@ -77,48 +77,24 @@ do_stop()
>> >>
>> >> case "$1"
in
>> >> start)
>> >> @@ -52,6 +67,7 @@ diff -ur
git.org/pi-blaster.boot.sh [2]
>> >> git/pi-blaster.boot.sh [3]
>> >> #
'force-reload' alias
>> >> #
>> >> - log_daemon_msg "Restarting $DESC"
"$NAME"
>> >> ++ echo "Restarting $DESC" "$NAME"
>> >> do_stop
>> >> -
case "$?" in
>> >> - 0|1)
>> >> @@ -67,11 +83,14 @@ diff -ur
git.org/pi-blaster.boot.sh [2]
>> >> git/pi-blaster.boot.sh [3]
>> >> -
log_end_msg 1
>> >> - ;;
>> >> - esac
>> >> -+ do_start
>> >> ++
do_start
>> >> ;;
>> >> *)
>> >> - echo "Usage: $SCRIPTNAME
{start|stop|status|restart|force-reload}"
>> >> >&2
>> >> -+ echo
"Usage: $SCRIPTNAME {start|stop|restart}" >&2
>> >> ++ echo "Usage:
$SCRIPTNAME {start|stop|restart|force-reload}" >&2
>> >> exit 3
>> >>
;;
>> >> esac
>> >> +--
>> >> +1.9.1
>> >> +
>> >> diff --git
a/recipes-devtools/pi-blaster/pi-blaster.inc
>> >>
b/recipes-devtools/pi-blaster/pi-blaster.inc
>> >> index
a3beccc..a548957 100644
>> >> ---
a/recipes-devtools/pi-blaster/pi-blaster.inc
>> >> +++
b/recipes-devtools/pi-blaster/pi-blaster.inc
>> >> @@ -2,7 +2,7 @@
DESCRIPTION = "This project enables PWM on the GPIO pins
>> >> you
request of a Raspbe
>> >> HOMEPAGE =
"https://github.com/sarfata/pi-blaster/ [4]"
>> >> SECTION =
"devel/libs"
>> >> LICENSE = "MIT"
>> >> -LIC_FILES_CHKSUM =
>> >>
"file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
>>
>> +LIC_FILES_CHKSUM =
>> >>
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
>>
>
>> >
>> > What changed here ?
>> >
>> > The license is added in the
end of the README.md so in this case some
>> > additional description +
modifications earlier in the README.md caused the
>> > license text to
move place. When it comes to the license text I could only
>> > find
changes in whitespace and newlines. They seems to have been caused by
>>
> the pi-blaster commit: '0e1a1df Cleaning up the README'
>> >
>> > BR
Petter
>> >
>> > $ diff -Naur ec5e1b4c.README.md [5] README.md | tail -n
38
>> >
>> 
>> perfect add few lines to the commit message about this
>

> That would be nice.

Agree, I will

[yocto] [meta-raspberrypi][PATCH v2] pi-blaster: update to include proper rpi3 support

2017-06-08 Thread Petter Mabäcker
Update to latest available revision, in order to include proper rpi3
support as well as latest fixes.

LIC_FILES_CHKSUM for the license text in README.md is changed to handle
fixes of whitespace and newlines in the license text, introduced by the
pi-blaster commit: '0e1a1df Cleaning up the README'.

Signed-off-by: Petter Mabäcker 
---
 .../files/remove-initscript-lsb-dependency.patch   | 37 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  2 +-
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 3 files changed, 30 insertions(+), 11 deletions(-)

diff --git 
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch 
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
index 7ea9a3b..c8afe60 100644
--- a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
+++ b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
@@ -1,13 +1,28 @@
-Remove dependencies on LSB functions
+From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Sun, 4 Jun 2017 12:22:40 +0200
+Subject: [PATCH] Remove dependencies on LSB functions
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+See this as a rebase of the previous 'Remove dependencies on LSB
+functions patch' with only minor modifications from the original version,
+based on the work done by Alex Lennon  in
+'25fd817 pi-blaster: Added recipe'.
 
 Upstream-Status: Inappropriate [configuration]
 
-Signed-off-by: Alex Lennon 
+Signed-off-by: Petter Mabäcker 
+---
+ debian/pi-blaster.init | 38 +++---
+ 1 file changed, 7 insertions(+), 31 deletions(-)
 
-diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 git.org/pi-blaster.boot.sh 2014-05-20 14:49:44.378582168 +0100
-+++ git/pi-blaster.boot.sh 2014-05-20 14:51:08.330582386 +0100
-@@ -28,12 +28,12 @@
+diff --git a/debian/pi-blaster.init b/debian/pi-blaster.init
+index b142d70..01a686c 100644
+--- a/debian/pi-blaster.init
 b/debian/pi-blaster.init
+@@ -28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
  [ -r /etc/default/$NAME ] && . /etc/default/$NAME
  
  # Load the VERBOSE setting and other rcS variables
@@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
  
  #
  # Function that starts the daemon/service
-@@ -77,48 +77,23 @@
+@@ -77,48 +77,24 @@ do_stop()
  
  case "$1" in
start)
@@ -52,6 +67,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
# 'force-reload' alias
#
 -  log_daemon_msg "Restarting $DESC" "$NAME"
++  echo "Restarting $DESC" "$NAME"
do_stop
 -  case "$?" in
 -0|1)
@@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 -  log_end_msg 1
 -  ;;
 -  esac
-+  do_start
++do_start
;;
*)
 -  echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
-+  echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
++  echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 3
;;
  esac
+-- 
+1.9.1
+
diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc 
b/recipes-devtools/pi-blaster/pi-blaster.inc
index a3beccc..a548957 100644
--- a/recipes-devtools/pi-blaster/pi-blaster.inc
+++ b/recipes-devtools/pi-blaster/pi-blaster.inc
@@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins you 
request of a Raspbe
 HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
 SECTION = "devel/libs"
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
+LIC_FILES_CHKSUM = 
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
 
 SRC_URI = "git://github.com/sarfata/pi-blaster \
file://remove-initscript-lsb-dependency.patch \
diff --git a/recipes-devtools/pi-blaster/pi-blaster_git.bb 
b/recipes-devtools/pi-blaster/pi-blaster_git.bb
index 263852b..ac812ab 100644
--- a/recipes-devtools/pi-blaster/pi-blaster_git.bb
+++ b/recipes-devtools/pi-blaster/pi-blaster_git.bb
@@ -1,3 +1,3 @@
 require pi-blaster.inc
 
-SRCREV = "ec5e1b4c6191d8f9a538497dbbb86f9cf0de7016"
+SRCREV = "9f45eb23a8a3b2d1c08d08a6d68f206fe91ecf4c"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Building boost-python

2017-06-08 Thread Jakob Hasse

Hey Tim,

I'm pretty sure that it works now with the ros-solution (haven't double 
checked and cleaned and what not).

So thanks!

Best Regards,
Jakob

On 08.06.2017 07:41, Tim Orling wrote:

You should do what meta-ros did:
https://github.com/bmwcarit/meta-ros/blob/master/recipes-support/boost/boost_%25.bbappend


On Jun 7, 2017, at 3:46 AM, Jakob Hasse 
> wrote:





On 07.06.2017 11:59, VanCutsem, Geoffroy wrote:



-Original Message-
From: yocto-boun...@yoctoproject.org 
 [mailto:yocto-
boun...@yoctoproject.org ] On 
Behalf Of Jakob Hasse

Sent: Wednesday, June 7, 2017 11:48 AM
To: Yocto List mailto:yocto@yoctoproject.org>>
Subject: [yocto] Building boost-python

Hello,

One of my layers needs boost-python.
When I try to build boost-python with bitbake, it complains:

ERROR: Nothing PROVIDES 'boost-python'

How can I fix this?
Boost itself builds and I also included
PACKAGECONFIG_pn_boost = "python"
without any effect.

I believe the correct spelling is:
PACKAGECONFIG_pn-boost = "python"
(note the hyphen instead of underscore)
Yes, I saw it somewhere else now with a hyphen, too, but even with 
the corrected local.conf, the problem still remains.

Bitbake quits with the same error message as before



My bblayers.conf is here:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf #
changes incompatibly LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
   /usr/local/dey-2.0/sources/poky/meta \
   /usr/local/dey-2.0/sources/poky/meta-yocto \
   /usr/local/dey-2.0/sources/poky/meta-yocto-bsp \
   /usr/local/dey-2.0/sources/meta-openembedded/meta-oe \
   /usr/local/dey-2.0/sources/meta-openembedded/meta-python \
/usr/local/dey-2.0/sources/meta-openembedded/meta-networking \
/usr/local/dey-2.0/sources/meta-openembedded/meta-webserver \
   /usr/local/dey-2.0/sources/meta-qt5 \
   /usr/local/dey-2.0/sources/meta-swupdate \
   /usr/local/dey-2.0/sources/meta-fsl-arm \
   /usr/local/dey-2.0/sources/meta-fsl-demos \
   /usr/local/dey-2.0/sources/meta-digi/meta-digi-arm \
   /usr/local/dey-2.0/sources/meta-digi/meta-digi-dey \
   /usr/local/dey-2.0/sources/meta-java/ \
   /usr/local/dey-2.0/sources/meta-iot-cloud/ \

   "
BBLAYERS_NON_REMOVABLE ?= " \
   /usr/local/dey-2.0/sources/poky/meta \
   /usr/local/dey-2.0/sources/poky/meta-yocto \
   "

Any help is welcome!
Jakob

--
Jakob Hasse
Software Developement

E: jakob.ha...@smart-home-technology.ch 


T: +41 44 552 02 66

Smart Home Technology GmbH
www.smart-home-technology.ch 

--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto


--
Jakob Hasse
Software Developement

E: jakob.ha...@smart-home-technology.ch 


T: +41 44 552 02 66

Smart Home Technology GmbH
www.smart-home-technology.ch 

--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto


--
Jakob Hasse
Software Developement

E: jakob.ha...@smart-home-technology.ch
T: +41 44 552 02 66

Smart Home Technology GmbH
www.smart-home-technology.ch

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] dllmap config for a Mono app

2017-06-08 Thread Khem Raj
On Wed, Jun 7, 2017 at 11:41 PM, Craig McQueen
 wrote:
> I have a Mono app that uses DllImport to load some functions from libraries. 
> The app can't find the libraries unless I create a Mono config file 
> containing dllmap lines to map the library's plain "DLL" name (e.g. "foo") to 
> the real name of the .so file (e.g. "libfoo.so.4").
>
> * What would be a good way in the .bb recipe to automatically create the 
> required Mono config file? It would need to find the "real" names of the 
> library files from the library(s) build output. So it would DEPENDS on the 
> library(s).
>

mono.bbclass.

> * Is it better to create a local config file, or write it into 
> /etc/mono/config? (My Mono app has the DllImports in a compiled DLL, and so 
> far I've found that I need to create a local MyDll.dll.config file; making a 
> MyApp.exe.config file doesn't work.)

as long as it stays unique in rootfs you should be fine.

>
> * Alternatively, the Mono app can find the libraries if plain libfoo.so 
> symbolic link to libfoo.so.4 exists in the rootfs. But this symbolic link 
> normally is only in the libfoo-dev package, not the libfoo package. Is there 
> some reasonable way to create and install the libfoo.so symbolic links on the 
> rootfs?
>

.so are considered used for development so its usually a symlink to real
versioned .so or its a linker script in some projects. The default packaging
rules therefore considers it so as well. This is as I said most common case
but then there are packages where they use .so ( unversioned name) usually
dlopen/ cases ( e.g. gstreamer plugins )

> --
> Craig McQueen
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [PATCH] yocto-bsp: update reference BSPs to 4.1 latest

2017-06-08 Thread Bruce Ashfield
The reference BSPs are lagging on their 4.1 SRCREVs, which means
-stable updates, and gcc-7 build fixes are missing.

Signed-off-by: Bruce Ashfield 
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
index b308c8dfa1cc..afb04c28f4d1 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
@@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
 
 SRCREV_machine_genericx86?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
 SRCREV_machine_genericx86-64 ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
-SRCREV_machine_edgerouter ?= "2ce56d130ddff67f43ec857cc51cd347666a0078"
-SRCREV_machine_beaglebone ?= "235de25be3f143b91dcc69479b770722c508889e"
-SRCREV_machine_mpc8315e-rdb ?= "2ce56d130ddff67f43ec857cc51cd347666a0078"
+SRCREV_machine_edgerouter ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
+SRCREV_machine_beaglebone ?= "79414e2b0e0b7f5b86e358a907f841486f428079"
+SRCREV_machine_mpc8315e-rdb ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
-- 
2.5.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] LLVM linking for custom recipe

2017-06-08 Thread Giordon Stark
Hi,

I have the following error message when trying to get LLVM linked up. The
problem is that I'm using a widely used science software called ROOT (
https://root.cern.ch/) with the following minimal recipe at the moment (
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb)
however I get the following error...

Any ideas?

Giordon

| CMake Error at cmake/modules/SearchInstalledSoftware.cmake:662
(find_package):
|   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this project has
|   asked CMake to find a package configuration file provided by "LLVM", but
|   CMake did not find one.
|
|   Could not find a package configuration file provided by "LLVM" with any
of
|   the following names:
|
| LLVMConfig.cmake
| llvm-config.cmake
|
|   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
|   "LLVM_DIR" to a directory containing one of the above files.  If "LLVM"
|   provides a separate development package or SDK, be sure it has been
|   installed.
| Call Stack (most recent call first):
|   CMakeLists.txt:58 (include)
|
|
| -- Configuring incomplete, errors occurred!
| See also
"/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeOutput.log".
| See also
"/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeError.log".
| WARNING:
/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/run.do_configure.16761:1
exit 1 from 'cmake ${OECMAKE_SITEFILE}
/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/root-6.04.12
-DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin
-DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec
-DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
-DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com
-DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib
-DCMAKE_INSTALL_INCLUDEDIR:PATH=include
-DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0
-DCMAKE_TOOLCHAIN_FILE=/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/toolchain.cmake
-DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 -Drootfit=ON
-Dminuit2=ON -Dpython=ON -Dssl=ON -Dxrootd=ON -Dbuiltin_freetype=ON
-Dbuiltin_llvm=OFF ${PACKAGECONFIG_CONFARGS} -Wno-dev'
| ERROR: Function failed: do_configure (log file is located at
/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/log.do_configure.16761)
ERROR: Task 
(/local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1027 tasks of which 1024 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
  /local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] LLVM linking for custom recipe

2017-06-08 Thread Khem Raj
On Thu, Jun 8, 2017 at 1:42 PM, Giordon Stark  wrote:
> Hi,
>
> I have the following error message when trying to get LLVM linked up. The
> problem is that I'm using a widely used science software called ROOT
> (https://root.cern.ch/) with the following minimal recipe at the moment
> (https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb)
> however I get the following error...
>
> Any ideas?

Look into meta-clang there are patches for cross compiling clang/llvm
https://github.com/kraj/meta-clang

>
> Giordon
>
> | CMake Error at cmake/modules/SearchInstalledSoftware.cmake:662
> (find_package):
> |   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this project has
> |   asked CMake to find a package configuration file provided by "LLVM", but
> |   CMake did not find one.
> |
> |   Could not find a package configuration file provided by "LLVM" with any
> of
> |   the following names:
> |
> | LLVMConfig.cmake
> | llvm-config.cmake
> |
> |   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
> |   "LLVM_DIR" to a directory containing one of the above files.  If "LLVM"
> |   provides a separate development package or SDK, be sure it has been
> |   installed.
> | Call Stack (most recent call first):
> |   CMakeLists.txt:58 (include)
> |
> |
> | -- Configuring incomplete, errors occurred!
> | See also
> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeOutput.log".
> | See also
> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeError.log".
> | WARNING:
> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/run.do_configure.16761:1
> exit 1 from 'cmake ${OECMAKE_SITEFILE}
> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/root-6.04.12
> -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin
> -DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec
> -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
> -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com
> -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib
> -DCMAKE_INSTALL_INCLUDEDIR:PATH=include
> -DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0
> -DCMAKE_TOOLCHAIN_FILE=/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/toolchain.cmake
> -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 -Drootfit=ON
> -Dminuit2=ON -Dpython=ON -Dssl=ON -Dxrootd=ON -Dbuiltin_freetype=ON
> -Dbuiltin_llvm=OFF ${PACKAGECONFIG_CONFARGS} -Wno-dev'
> | ERROR: Function failed: do_configure (log file is located at
> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/log.do_configure.16761)
> ERROR: Task
> (/local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 1027 tasks of which 1024 didn't need to be
> rerun and 1 failed.
>
> Summary: 1 task failed:
>   /local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] LLVM linking for custom recipe

2017-06-08 Thread Giordon Stark
Hi Khem,

Which recipe? My problem is that ROOT's CMake is unable to find the
cross-compiled LLVM, and I'm not sure how to get it to find it.

Giordon

On Thu, Jun 8, 2017 at 3:47 PM Khem Raj  wrote:

> On Thu, Jun 8, 2017 at 1:42 PM, Giordon Stark  wrote:
> > Hi,
> >
> > I have the following error message when trying to get LLVM linked up. The
> > problem is that I'm using a widely used science software called ROOT
> > (https://root.cern.ch/) with the following minimal recipe at the moment
> > (
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
> )
> > however I get the following error...
> >
> > Any ideas?
>
> Look into meta-clang there are patches for cross compiling clang/llvm
> https://github.com/kraj/meta-clang
>
> >
> > Giordon
> >
> > | CMake Error at cmake/modules/SearchInstalledSoftware.cmake:662
> > (find_package):
> > |   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this project
> has
> > |   asked CMake to find a package configuration file provided by "LLVM",
> but
> > |   CMake did not find one.
> > |
> > |   Could not find a package configuration file provided by "LLVM" with
> any
> > of
> > |   the following names:
> > |
> > | LLVMConfig.cmake
> > | llvm-config.cmake
> > |
> > |   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
> > |   "LLVM_DIR" to a directory containing one of the above files.  If
> "LLVM"
> > |   provides a separate development package or SDK, be sure it has been
> > |   installed.
> > | Call Stack (most recent call first):
> > |   CMakeLists.txt:58 (include)
> > |
> > |
> > | -- Configuring incomplete, errors occurred!
> > | See also
> >
> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeOutput.log".
> > | See also
> >
> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeError.log".
> > | WARNING:
> >
> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/run.do_configure.16761:1
> > exit 1 from 'cmake ${OECMAKE_SITEFILE}
> >
> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/root-6.04.12
> > -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin
> > -DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec
> > -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
> > -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com
> > -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib
> > -DCMAKE_INSTALL_INCLUDEDIR:PATH=include
> > -DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0
> >
> -DCMAKE_TOOLCHAIN_FILE=/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/toolchain.cmake
> > -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 -Drootfit=ON
> > -Dminuit2=ON -Dpython=ON -Dssl=ON -Dxrootd=ON -Dbuiltin_freetype=ON
> > -Dbuiltin_llvm=OFF ${PACKAGECONFIG_CONFARGS} -Wno-dev'
> > | ERROR: Function failed: do_configure (log file is located at
> >
> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/log.do_configure.16761)
> > ERROR: Task
> > (/local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure)
> > failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 1027 tasks of which 1024 didn't need to be
> > rerun and 1 failed.
> >
> > Summary: 1 task failed:
> >   /local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure
> > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH v2] poky-cgl: avoid installing multiple syslogs

2017-06-08 Thread jackie.huang
From: Jackie Huang 

do_rootfs fails if multiple syslogs are installed:
| Error: package syslog-ng-3.8.1-r0.i586 conflicts with sysklogd provided
  by sysklogd-1.5.1-r0.i586

core-image-cgl requires packagegroup-core-full-cmdline which depends
on VIRTUAL-RUNTIME_syslog (default to sysklogd), so set the
VIRTUAL-RUNTIME_syslog in distro conf and no need to depends
on any syslog in packagegroup-cgl-applications, then we ensure
that only one syslog is installed to avoid conflicts.

Signed-off-by: Jackie Huang 
---
 meta-cgl-common/conf/distro/poky-cgl.conf  | 4 
 meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb | 2 --
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta-cgl-common/conf/distro/poky-cgl.conf 
b/meta-cgl-common/conf/distro/poky-cgl.conf
index 90cc82b..69f6200 100644
--- a/meta-cgl-common/conf/distro/poky-cgl.conf
+++ b/meta-cgl-common/conf/distro/poky-cgl.conf
@@ -5,3 +5,7 @@ DISTRO = "poky-cgl"
 
 IMAGE_CLASSES += "image_types_uboot"
 PREFERRED_PROVIDER_virtual/refpolicy="refpolicy-targeted"
+
+# we want to use rsyslog as the default syslog, but it's GPLv3, so need this
+# check to switch to syslog-ng if GLPv3 is blacklisted.
+VIRTUAL-RUNTIME_syslog ?= "${@bb.utils.contains('INCOMPATIBLE_LICENSE', 
'GPLv3', 'syslog-ng', 'rsyslog', d)}"
diff --git a/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb 
b/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb
index a64065b..5e7170d 100644
--- a/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb
+++ b/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb
@@ -40,7 +40,6 @@ RDEPENDS_${PN} = " \
 quota \
 smartmontools \
 monit \
-syslog-ng \
 ocfs2-tools \
 logcheck \
 samhain-client \
@@ -49,7 +48,6 @@ RDEPENDS_${PN} = " \
 crash \
 pam-passwdqc \
 libpam \
-rsyslog \
 makedumpfile \
 "
 
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] LLVM linking for custom recipe

2017-06-08 Thread Giordon Stark
Looking into more details, I don't know or where bitbake tries to look for
things as things get compiled (flags, environment, etc)... but the error
message does say ROOT is looking for

LLVMConfig.cmake
llvm-config.cmake

However, I see

tmp/work/aarch64-poky-linux/llvm3.3/3.3-r0/llvm-3.3.src/cmake/modules/LLVM-Config.cmake

which is perhaps why it can't find it. I assume the output name here isn't
100% compatible, and I'm using meta-oe's llvm3.3. I'm just mostly stuck on
CMake's default behavior here, I think.

Giordon

On Thu, Jun 8, 2017 at 4:37 PM Giordon Stark  wrote:

> Hi Khem,
>
> Which recipe? My problem is that ROOT's CMake is unable to find the
> cross-compiled LLVM, and I'm not sure how to get it to find it.
>
> Giordon
>
> On Thu, Jun 8, 2017 at 3:47 PM Khem Raj  wrote:
>
>> On Thu, Jun 8, 2017 at 1:42 PM, Giordon Stark  wrote:
>> > Hi,
>> >
>> > I have the following error message when trying to get LLVM linked up.
>> The
>> > problem is that I'm using a widely used science software called ROOT
>> > (https://root.cern.ch/) with the following minimal recipe at the moment
>> > (
>> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
>> )
>> > however I get the following error...
>> >
>> > Any ideas?
>>
>> Look into meta-clang there are patches for cross compiling clang/llvm
>> https://github.com/kraj/meta-clang
>>
>> >
>> > Giordon
>> >
>> > | CMake Error at cmake/modules/SearchInstalledSoftware.cmake:662
>> > (find_package):
>> > |   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this project
>> has
>> > |   asked CMake to find a package configuration file provided by
>> "LLVM", but
>> > |   CMake did not find one.
>> > |
>> > |   Could not find a package configuration file provided by "LLVM" with
>> any
>> > of
>> > |   the following names:
>> > |
>> > | LLVMConfig.cmake
>> > | llvm-config.cmake
>> > |
>> > |   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
>> > |   "LLVM_DIR" to a directory containing one of the above files.  If
>> "LLVM"
>> > |   provides a separate development package or SDK, be sure it has been
>> > |   installed.
>> > | Call Stack (most recent call first):
>> > |   CMakeLists.txt:58 (include)
>> > |
>> > |
>> > | -- Configuring incomplete, errors occurred!
>> > | See also
>> >
>> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeOutput.log".
>> > | See also
>> >
>> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeError.log".
>> > | WARNING:
>> >
>> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/run.do_configure.16761:1
>> > exit 1 from 'cmake ${OECMAKE_SITEFILE}
>> >
>> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/root-6.04.12
>> > -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin
>> > -DCMAKE_INSTALL_SBINDIR:PATH=sbin
>> -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec
>> > -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
>> > -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com
>> > -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib
>> > -DCMAKE_INSTALL_INCLUDEDIR:PATH=include
>> > -DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0
>> >
>> -DCMAKE_TOOLCHAIN_FILE=/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/toolchain.cmake
>> > -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1
>> -Drootfit=ON
>> > -Dminuit2=ON -Dpython=ON -Dssl=ON -Dxrootd=ON -Dbuiltin_freetype=ON
>> > -Dbuiltin_llvm=OFF ${PACKAGECONFIG_CONFARGS} -Wno-dev'
>> > | ERROR: Function failed: do_configure (log file is located at
>> >
>> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/log.do_configure.16761)
>> > ERROR: Task
>> > (/local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure)
>> > failed with exit code '1'
>> > NOTE: Tasks Summary: Attempted 1027 tasks of which 1024 didn't need to
>> be
>> > rerun and 1 failed.
>> >
>> > Summary: 1 task failed:
>> >   /local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure
>> > Summary: There was 1 ERROR message shown, returning a non-zero exit
>> code.
>> >
>> >
>> > --
>> > ___
>> > yocto mailing list
>> > yocto@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto
>> >
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-cgl][PATCH] poky-cgl: avoid installing multiple syslogs

2017-06-08 Thread Huang, Jie (Jackie)


> -Original Message-
> From: Adrian Dudau [mailto:adrian.du...@enea.com]
> Sent: Thursday, June 08, 2017 20:01
> To: Huang, Jie (Jackie); yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-cgl][PATCH] poky-cgl: avoid installing multiple
> syslogs
> 
> On fre, 2017-06-02 at 15:59 +0800, jackie.hu...@windriver.com wrote:
> > From: Jackie Huang 
> >
> > do_rootfs fails if multiple syslogs are installed:
> > >
> > > Error: package syslog-ng-3.8.1-r0.i586 conflicts with sysklogd
> > > provided
> >   by sysklogd-1.5.1-r0.i586
> >
> > core-image-cgl requires packagegroup-core-full-cmdline which depends
> > on VIRTUAL-RUNTIME_syslog (default to sysklogd), so set the
> > VIRTUAL-RUNTIME_syslog in distro conf and no need to depends
> > on any syslog in packagegroup-cgl-applications, then we ensure
> > that only one syslog is installed to avoid conflicts.
> >
> > Signed-off-by: Jackie Huang 
> > ---
> >  meta-cgl-common/conf/distro/poky-cgl.conf  | 4
> > 
> >  meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb | 2
> > --
> >  2 files changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta-cgl-common/conf/distro/poky-cgl.conf b/meta-cgl-
> > common/conf/distro/poky-cgl.conf
> > index 90cc82b..69f6200 100644
> > --- a/meta-cgl-common/conf/distro/poky-cgl.conf
> > +++ b/meta-cgl-common/conf/distro/poky-cgl.conf
> > @@ -5,3 +5,7 @@ DISTRO = "poky-cgl"
> >
> >  IMAGE_CLASSES += "image_types_uboot"
> >  PREFERRED_PROVIDER_virtual/refpolicy="refpolicy-targeted"
> > +
> > +# we want to use rsyslog as the default syslog, but it's GPLv3, so
> > need this
> > +# check to switch to syslog-ng if GLPv3 is blacklisted.
> > +VIRTUAL-RUNTIME_syslog ?= "${@bb.utils.contains('INCOMPATIBLE_LICENS
> > E', 'GPLv3', 'syslog-ng', 'rsyslog', d)}"
> > diff --git a/meta-cgl-common/packagegroups/packagegroup-cgl-
> > applications.bb b/meta-cgl-common/packagegroups/packagegroup-cgl-
> > applications.bb
> > index b566e2d..be36075 100644
> > --- a/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb
> > +++ b/meta-cgl-common/packagegroups/packagegroup-cgl-applications.bb
> > @@ -40,7 +40,6 @@ RDEPENDS_${PN} = " \
> >  quota \
> >  smartmontools \
> >  monit \
> > -syslog-ng \
> >  ocfs2-tools \
> >  logcheck \
> >  samhain-client \
> > @@ -48,7 +47,6 @@ RDEPENDS_${PN} = " \
> >  audit \
> >  pam-passwdqc \
> >  libpam \
> > -rsyslog \
> >  makedumpfile \
> >  "
> >
> > --
> > 2.11.0
> >
> 
> Patch   good but doesn't apply. Please rebase on origin/master and send
> again.

Rebased and re-sent as v2.

Thanks,
Jackie

> 
> best regards
> --Adrian
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH 0/4 v2] resource-agents: update to 1.1.16 and several fixes

2017-06-08 Thread jackie.huang
From: Jackie Huang 

v2 comments:
rebased and fixed the conflicts.

--
The following changes since commit 0296ce6a32e9b130af347267850940b189b78675:

  cluster-glue: update useradd parameters (2017-06-08 15:10:31 +0200)

are available in the git repository at:

  https://github.com/jackiehjm/meta-cgl.git 
jhuang0/up_resource-agents-v2_170609_0
  https://github.com//tree/jhuang0/up_resource-agents-v2_170609_0

Jackie Huang (4):
  resource-agents: fix dependencies
  resource-agents: fix install-sh not found
  resource-agents: fix builds error when S != B
  resource-agents: update to version 4.0.1

 .../resource-agents/fix-install-sh-not-found.patch | 60 ++
 ...uilds-when-srcdir-and-builddir-are-sepera.patch | 39 ++
 ...ce-agents_3.9.7.bb => resource-agents_4.0.1.bb} | 18 +--
 3 files changed, 114 insertions(+), 3 deletions(-)
 create mode 100644 
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fix-install-sh-not-found.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fs.sh-fix-builds-when-srcdir-and-builddir-are-sepera.patch
 rename 
meta-cgl-common/recipes-cgl/cluster-resource-agents/{resource-agents_3.9.7.bb 
=> resource-agents_4.0.1.bb} (83%)

-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH 1/4 v2] resource-agents: fix dependencies

2017-06-08 Thread jackie.huang
From: Jackie Huang 

* Add missing runtime dependencies for:
  - many tools and scripts need bash and perl.
  - lvm.sh requires: lvm2
  - ip.sh requires: ethtool iproute2 iputils-arping
  - fs.sh requires: e2fsprogs-e2fsck util-linux quota
  - netfs.sh requires: procps util-linux nfs-utils

Signed-off-by: Jackie Huang 
---
 .../cluster-resource-agents/resource-agents_3.9.7.bb | 12 +++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
index e6f127b..2e8b8f1 100644
--- 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
+++ 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
@@ -28,7 +28,17 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
 file://COPYING.GPLv3;md5=d32239bcb673463ab874e80d47fae504"
 
 DEPENDS = "cluster-glue"
-RDEPENDS_${PN} += "bash"
+
+# There are many tools and scripts that need bash and perl.
+# lvm.sh requires: lvm2
+# ip.sh requires: ethtool iproute2 iputils-arping
+# fs.sh requires: e2fsprogs-e2fsck util-linux quota
+# netfs.sh requires: procps util-linux nfs-utils
+RDEPENDS_${PN} += "bash perl lvm2 \
+ethtool iproute2 iputils-arping \
+e2fsprogs-e2fsck util-linux quota \
+procps nfs-utils \
+"
 
 inherit autotools systemd pkgconfig
 
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH 4/4 v2] resource-agents: update to version 4.0.1

2017-06-08 Thread jackie.huang
From: Jackie Huang 

Signed-off-by: Jackie Huang 
---
 .../{resource-agents_3.9.7.bb => resource-agents_4.0.1.bb}| 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename 
meta-cgl-common/recipes-cgl/cluster-resource-agents/{resource-agents_3.9.7.bb 
=> resource-agents_4.0.1.bb} (96%)

diff --git 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.0.1.bb
similarity index 96%
rename from 
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
rename to 
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.0.1.bb
index 2f36b1b..2a9643b 100644
--- 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
+++ 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.0.1.bb
@@ -22,8 +22,8 @@ SRC_URI = 
"https://codeload.github.com/ClusterLabs/resource-agents/tar.gz/v${PV}
file://fs.sh-fix-builds-when-srcdir-and-builddir-are-sepera.patch \
   "
 
-SRC_URI[md5sum] = "c59096b1bacc704e8a5a285f15729109"
-SRC_URI[sha256sum] = 
"e5bd62658fbc236acb83b709f64b2cd9fae52aa4a420a44fed5eb667e928b152"
+SRC_URI[md5sum] = "8530431861e659d4ce2f04afcc4efc03"
+SRC_URI[sha256sum] = 
"863f83c724bad3a8bcff12b9c8712406c43e010041868826cad7b78fd8cfb9fb"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
 file://COPYING.LGPL;md5=4fbd65380cdd255951079008b364516c \
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH 3/4 v2] resource-agents: fix builds error when S != B

2017-06-08 Thread jackie.huang
From: Jackie Huang 

It fails to find fs.sh.in when srddir and builddir are not the same:

make[5]: Entering directory '/path/to/builddir/rgmanager/src/resources'
cat fs.sh.in | sed \
-e 's#@''LOGDIR@#/var/log/cluster#g' \
> fs.sh.out
cat: fs.sh.in: No such file or directorychmod +x fs.sh.out
mv fs.sh.out fs.sh

Add abs_srcdir to fix this.

Signed-off-by: Jackie Huang 
---
 ...uilds-when-srcdir-and-builddir-are-sepera.patch | 39 ++
 .../resource-agents_3.9.7.bb   |  1 +
 2 files changed, 40 insertions(+)
 create mode 100644 
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fs.sh-fix-builds-when-srcdir-and-builddir-are-sepera.patch

diff --git 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fs.sh-fix-builds-when-srcdir-and-builddir-are-sepera.patch
 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fs.sh-fix-builds-when-srcdir-and-builddir-are-sepera.patch
new file mode 100644
index 000..3247927
--- /dev/null
+++ 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fs.sh-fix-builds-when-srcdir-and-builddir-are-sepera.patch
@@ -0,0 +1,39 @@
+From 5b7a84dbb9d06112c4b2804223163d91ba8ab786 Mon Sep 17 00:00:00 2001
+From: Jackie Huang 
+Date: Thu, 1 Jun 2017 10:34:38 +0800
+Subject: [PATCH] fs.sh: fix builds when srcdir and builddir are seperated
+
+It fails to find fs.sh.in when srddir and builddir are not the same:
+
+make[5]: Entering directory '/path/to/builddir/rgmanager/src/resources'
+cat fs.sh.in | sed \
+-e 's#@''LOGDIR@#/var/log/cluster#g' \
+> fs.sh.out
+cat: fs.sh.in: No such file or directorychmod +x fs.sh.out
+mv fs.sh.out fs.sh
+
+Add abs_srcdir to fix this.
+
+Upstream-Status: Submitted 
[https://github.com/ClusterLabs/resource-agents/pull/986]
+
+Signed-off-by: Jackie Huang 
+---
+ rgmanager/src/resources/Makefile.am | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/rgmanager/src/resources/Makefile.am 
b/rgmanager/src/resources/Makefile.am
+index de88c69..30b3be9 100644
+--- a/rgmanager/src/resources/Makefile.am
 b/rgmanager/src/resources/Makefile.am
+@@ -68,7 +68,7 @@ rngdir   = ${CLUSTERDATA}/relaxng
+ rng_DATA  = $(DTD) $(XSL) $(RESRNG)
+ 
+ $(TARGET):
+-  cat $@.in | sed \
++  cat $(abs_srcdir)/$@.in | sed \
+   -e 's#@''LOGDIR@#${LOGDIR}#g' \
+   > $@.out
+   chmod +x $@.out
+-- 
+2.11.0
+
diff --git 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
index 2d2dd88..2f36b1b 100644
--- 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
+++ 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
@@ -19,6 +19,7 @@ SRC_URI = 
"https://codeload.github.com/ClusterLabs/resource-agents/tar.gz/v${PV}
file://02-set-OCF_ROOT_DIR-to-libdir-ocf.patch \
file://03-fix-header-defs-lookup.patch \
file://fix-install-sh-not-found.patch \
+   file://fs.sh-fix-builds-when-srcdir-and-builddir-are-sepera.patch \
   "
 
 SRC_URI[md5sum] = "c59096b1bacc704e8a5a285f15729109"
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH 2/4 v2] resource-agents: fix install-sh not found

2017-06-08 Thread jackie.huang
From: Jackie Huang 

Fix configure.ac to cope with new autoconf.
Recent autoconfs generate a bad configure when AM_INIT_AUTOMAKE is
called as late as it was, ending up thinking that the am_aux_dir is pwd
at the start of the build. Move it up to under AC_INIT to fix that.

configure.ac calls AM_INIT_AUTOMAKE too late. The attached patch moves
it up to just after AC_INIT, fixing the FTBFS.

Signed-off-by: Hongxu Jia 
Signed-off-by: Jackie Huang 
---
 .../resource-agents/fix-install-sh-not-found.patch | 60 ++
 .../resource-agents_3.9.7.bb   |  1 +
 2 files changed, 61 insertions(+)
 create mode 100644 
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fix-install-sh-not-found.patch

diff --git 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fix-install-sh-not-found.patch
 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fix-install-sh-not-found.patch
new file mode 100644
index 000..102b797
--- /dev/null
+++ 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents/fix-install-sh-not-found.patch
@@ -0,0 +1,60 @@
+configure.ac: fix install-sh not found
+
+Fix configure.ac to cope with new autoconf.
+Recent autoconfs generate a bad configure when AM_INIT_AUTOMAKE is
+called as late as it was, ending up thinking that the am_aux_dir is pwd
+at the start of the build. Move it up to under AC_INIT to fix that.
+
+Author: William Grant 
+
+Upstream-Status: Pending
+
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724116
+
+Signed-off-by: Hongxu Jia 
+---
+ configure.ac | 15 ---
+ 1 file changed, 8 insertions(+), 7 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index e8e2a7b..f3c8b9f 100644
+--- a/configure.ac
 b/configure.ac
+@@ -23,13 +23,20 @@ AC_INIT([resource-agents],
+   m4_esyscmd([make/git-version-gen .tarball-version]),
+   [to_be_defi...@foobar.org])
+ 
++AC_CONFIG_AUX_DIR(.)
++
++dnl
++dnl AM_INIT_AUTOMAKE([1.11.1 foreign dist-bzip2 dist-xz])
++dnl
++
++AM_INIT_AUTOMAKE([1.10.1 foreign dist-bzip2])
++
+ AC_USE_SYSTEM_EXTENSIONS
+ 
+ CRM_DTD_VERSION="1.0"
+ 
+ PKG_FEATURES=""
+ 
+-AC_CONFIG_AUX_DIR(.)
+ AC_CANONICAL_HOST
+ 
+ dnl Where #defines go (e.g. `AC_CHECK_HEADERS' below)
+@@ -56,12 +63,6 @@ AC_ARG_WITH(pkg-name,
+ [  --with-pkg-name=name Override package name (if you're a packager 
needing to pretend) ],
+ [ PACKAGE_NAME="$withval" ])
+ 
+-dnl 
+-dnl AM_INIT_AUTOMAKE([1.11.1 foreign dist-bzip2 dist-xz])
+-dnl
+-
+-AM_INIT_AUTOMAKE([1.10.1 foreign dist-bzip2])
+-
+ AC_DEFINE_UNQUOTED(AGENTS_VERSION, "$PACKAGE_VERSION", Current agents version)
+ 
+ CC_IN_CONFIGURE=yes
+-- 
+1.8.1.2
+
diff --git 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
index 2e8b8f1..2d2dd88 100644
--- 
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
+++ 
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
@@ -18,6 +18,7 @@ SRC_URI = 
"https://codeload.github.com/ClusterLabs/resource-agents/tar.gz/v${PV}
file://01-disable-doc-build.patch \
file://02-set-OCF_ROOT_DIR-to-libdir-ocf.patch \
file://03-fix-header-defs-lookup.patch \
+   file://fix-install-sh-not-found.patch \
   "
 
 SRC_URI[md5sum] = "c59096b1bacc704e8a5a285f15729109"
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-cgl][PATCH 0/4] resource-agents: update to 4.0.1 and several fixes

2017-06-08 Thread Huang, Jie (Jackie)


> -Original Message-
> From: Adrian Dudau [mailto:adrian.du...@enea.com]
> Sent: Thursday, June 08, 2017 22:32
> To: Huang, Jie (Jackie); yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-cgl][PATCH 0/4] resource-agents: update to 4.0.1
> and several fixes
> 
> On fre, 2017-06-02 at 16:21 +0800, jackie.hu...@windriver.com wrote:
> > From: Jackie Huang 
> >
> > --
> > The following changes since commit
> > c0afa706e9cdb650c0e8bb79f503743632350b00:
> >
> >   core-image-cgl: Remove ROOTFS_PKGMANAGE_BOOTSTRAP (2017-05-24
> > 14:19:13 +0200)
> >
> > are available in the git repository at:
> >
> >   https://github.com/jackiehjm/meta-cgl.git jhuang0/up_resource-
> > agents_170602_0
> >   https://github.com//tree/jhuang0/up_resource-agents_170602_0
> >
> > Jackie Huang (4):
> >   resource-agents: fix dependencies
> >   resource-agents: fix install-sh not found
> >   resource-agents: fix builds error when S != B
> >   resource-agents: update to version 4.0.1
> >
> >  .../resource-agents/fix-install-sh-not-found.patch | 60
> > ++
> >  ...uilds-when-srcdir-and-builddir-are-sepera.patch | 39
> > ++
> >  ...ce-agents_3.9.7.bb => resource-agents_4.0.1.bb} | 20 ++--
> >  3 files changed, 115 insertions(+), 4 deletions(-)
> >  create mode 100644 meta-cgl-common/recipes-cgl/cluster-resource-
> > agents/resource-agents/fix-install-sh-not-found.patch
> >  create mode 100644 meta-cgl-common/recipes-cgl/cluster-resource-
> > agents/resource-agents/fs.sh-fix-builds-when-srcdir-and-builddir-are-
> > sepera.patch
> >  rename meta-cgl-common/recipes-cgl/cluster-resource-
> > agents/{resource-agents_3.9.7.bb => resource-agents_4.0.1.bb} (82%)
> >
> > --
> > 2.11.0
> >
> 
> Same here, patchset is ok but you need to rebase on top of master
> latest.

Rebased and re-sent as v2.

Thanks,
Jackie

> 
> Best regards,
> --Adrian
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-gplv2][PATCH] msmtp: add old version with gplv2

2017-06-08 Thread jackie.huang
From: Jackie Huang 

msmtp changed to gplv3 from 1.4.13

Signed-off-by: Jackie Huang 
---
 .../msmtp-fixup-api-and-compiler-warning.patch | 244 +
 .../files/msmtp-replace-deprecated-function.patch  |  60 +
 recipes-extended/msmtp/msmtp_1.4.12.bb |  35 +++
 3 files changed, 339 insertions(+)
 create mode 100644 
recipes-extended/msmtp/files/msmtp-fixup-api-and-compiler-warning.patch
 create mode 100644 
recipes-extended/msmtp/files/msmtp-replace-deprecated-function.patch
 create mode 100644 recipes-extended/msmtp/msmtp_1.4.12.bb

diff --git 
a/recipes-extended/msmtp/files/msmtp-fixup-api-and-compiler-warning.patch 
b/recipes-extended/msmtp/files/msmtp-fixup-api-and-compiler-warning.patch
new file mode 100644
index 000..14c95d7
--- /dev/null
+++ b/recipes-extended/msmtp/files/msmtp-fixup-api-and-compiler-warning.patch
@@ -0,0 +1,244 @@
+msmtp: fixup api and compiler warnings
+
+Upstream-Status: Inappropriate [upstream rewrote with GPLv3]
+
+Author: Morgan Little 
+Signed-off-by: Jackie Huang 
+
+diff -Naur msmtp-1.4.12.orig/configure.ac msmtp-1.4.12/configure.ac
+--- msmtp-1.4.12.orig/configure.ac
 msmtp-1.4.12/configure.ac
+@@ -40,8 +40,8 @@
+ dnl System
+ case "${target}" in *-*-mingw32*) windows=yes ;; *) windows=no ;; esac
+ 
+-dnl gnulib 
+-gl_INIT
++#dnl gnulib 
++#gl_INIT
+ 
+ dnl Gettext
+ AM_GNU_GETTEXT([external])
+diff -Naur msmtp-1.4.12.orig/gnulib/base64.c msmtp-1.4.12/gnulib/base64.c
+--- msmtp-1.4.12.orig/gnulib/base64.c
 msmtp-1.4.12/gnulib/base64.c
+@@ -64,8 +64,8 @@
+possible.  If OUTLEN is larger than BASE64_LENGTH(INLEN), also zero
+terminate the output buffer. */
+ void
+-base64_encode (const char *restrict in, size_t inlen,
+- char *restrict out, size_t outlen)
++base64_encode (const char *in, size_t inlen,
++ char *out, size_t outlen)
+ {
+   static const char b64str[64] =
+ "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
+@@ -310,8 +310,8 @@
+that, when applicable, you must remove any line terminators that is
+part of the data stream before calling this function.  */
+ bool
+-base64_decode (const char *restrict in, size_t inlen,
+- char *restrict out, size_t *outlen)
++base64_decode (const char *in, size_t inlen,
++ char *out, size_t *outlen)
+ {
+   size_t outleft = *outlen;
+ 
+diff -Naur msmtp-1.4.12.orig/gnulib/base64.h msmtp-1.4.12/gnulib/base64.h
+--- msmtp-1.4.12.orig/gnulib/base64.h
 msmtp-1.4.12/gnulib/base64.h
+@@ -31,13 +31,13 @@
+ 
+ extern bool isbase64 (char ch);
+ 
+-extern void base64_encode (const char *restrict in, size_t inlen,
+- char *restrict out, size_t outlen);
++extern void base64_encode (const char *in, size_t inlen,
++ char *out, size_t outlen);
+ 
+ extern size_t base64_encode_alloc (const char *in, size_t inlen, char **out);
+ 
+-extern bool base64_decode (const char *restrict in, size_t inlen,
+- char *restrict out, size_t *outlen);
++extern bool base64_decode (const char *in, size_t inlen,
++ char *out, size_t *outlen);
+ 
+ extern bool base64_decode_alloc (const char *in, size_t inlen,
+char **out, size_t *outlen);
+diff -Naur msmtp-1.4.12.orig/gnulib/Makefile.am msmtp-1.4.12/gnulib/Makefile.am
+--- msmtp-1.4.12.orig/gnulib/Makefile.am
 msmtp-1.4.12/gnulib/Makefile.am
+@@ -59,20 +59,18 @@
+ 
+ ## begin gnulib module crypto/hmac-md5
+ 
++libgnu_a_SOURCES += hmac-md5.c
+ 
+ EXTRA_DIST += hmac-md5.c hmac.h
+ 
+-EXTRA_libgnu_a_SOURCES += hmac-md5.c
+-
+ ## end   gnulib module crypto/hmac-md5
+ 
+ ## begin gnulib module crypto/md5
+ 
++libgnu_a_SOURCES += md5.c
+ 
+ EXTRA_DIST += md5.c md5.h
+ 
+-EXTRA_libgnu_a_SOURCES += md5.c
+-
+ ## end   gnulib module crypto/md5
+ 
+ ## begin gnulib module getdelim
+@@ -149,11 +147,10 @@
+ 
+ ## begin gnulib module memxor
+ 
++libgnu_a_SOURCES += memxor.c
+ 
+ EXTRA_DIST += memxor.c memxor.h
+ 
+-EXTRA_libgnu_a_SOURCES += memxor.c
+-
+ ## end   gnulib module memxor
+ 
+ ## begin gnulib module size_max
+@@ -219,47 +216,6 @@
+ 
+ ## end   gnulib module stdint
+ 
+-## begin gnulib module stdio
+-
+-BUILT_SOURCES += stdio.h
+-
+-# We need the following in order to create  when the system
+-# doesn't have one that works with the given compiler.
+-stdio.h: stdio_.h
+-  rm -f $@-t $@
+-  { echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */' && \
+-sed -e 's|@''ABSOLUTE_STDIO_H''@|$(ABSOLUTE_STDIO_H)|g' \
+--e 's|@''GNULIB_FPRINTF_POSIX''@|$(GNULIB_FPRINTF_POSIX)|g' \
+--e 's|@''GNULIB_PRINTF_POSIX''@|$(GNULIB_PRINTF_POSIX)|g' \
+--e 's|@''GNULIB_SNPRINTF''@|$(GNULIB_SNPRINTF)|g' \
+--e 's|@''GNULIB_SPRINTF_POSIX''@|$(GNULIB_SPRINTF_POSIX)|g' \
+--e 's|@''GNULIB_VFPRINTF_POSIX''@|$(GNULIB_VFPRINTF_POSIX)|g' \
+--e 's|@''GNULIB_VPRINTF_POSIX''@|$(GNULIB_VPRINTF_POSIX)|g' \

Re: [yocto] [PATCH] yocto-bsp: update reference BSPs to 4.1 latest

2017-06-08 Thread Kevin Hao
On Thu, Jun 08, 2017 at 02:45:14PM -0400, Bruce Ashfield wrote:
> The reference BSPs are lagging on their 4.1 SRCREVs, which means
> -stable updates, and gcc-7 build fixes are missing.

I have made a patch to update the SRCREVs for 4.1, 4.4, 4,9 and 4.10 three 
weeks ago,
but it seems not get merged. I just sent a ping for the merging.

Thanks,
Kevin

> 
> Signed-off-by: Bruce Ashfield 
> ---
>  meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> index b308c8dfa1cc..afb04c28f4d1 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> @@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
>  
>  SRCREV_machine_genericx86?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
>  SRCREV_machine_genericx86-64 ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
> -SRCREV_machine_edgerouter ?= "2ce56d130ddff67f43ec857cc51cd347666a0078"
> -SRCREV_machine_beaglebone ?= "235de25be3f143b91dcc69479b770722c508889e"
> -SRCREV_machine_mpc8315e-rdb ?= "2ce56d130ddff67f43ec857cc51cd347666a0078"
> +SRCREV_machine_edgerouter ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
> +SRCREV_machine_beaglebone ?= "79414e2b0e0b7f5b86e358a907f841486f428079"
> +SRCREV_machine_mpc8315e-rdb ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
>  
>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> -- 
> 2.5.0
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH] yocto-bsp: update reference BSPs to 4.1 latest

2017-06-08 Thread Bruce Ashfield
On Thu, Jun 8, 2017 at 9:30 PM, Kevin Hao  wrote:

> On Thu, Jun 08, 2017 at 02:45:14PM -0400, Bruce Ashfield wrote:
> > The reference BSPs are lagging on their 4.1 SRCREVs, which means
> > -stable updates, and gcc-7 build fixes are missing.
>
> I have made a patch to update the SRCREVs for 4.1, 4.4, 4,9 and 4.10 three
> weeks ago,
> but it seems not get merged. I just sent a ping for the merging.
>
>
aha! Thanks for having taken care of that already Kevin. I *knew* I felt
like this was doing the same work again!

Bruce


> Thanks,
> Kevin
>
> >
> > Signed-off-by: Bruce Ashfield 
> > ---
> >  meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> > index b308c8dfa1cc..afb04c28f4d1 100644
> > --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> > +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> > @@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
> >
> >  SRCREV_machine_genericx86?= "398d1785c6bde0085b99f00f346e19
> 9a15fbdcef"
> >  SRCREV_machine_genericx86-64 ?= "398d1785c6bde0085b99f00f346e19
> 9a15fbdcef"
> > -SRCREV_machine_edgerouter ?= "2ce56d130ddff67f43ec857cc51cd347666a0078"
> > -SRCREV_machine_beaglebone ?= "235de25be3f143b91dcc69479b770722c508889e"
> > -SRCREV_machine_mpc8315e-rdb ?= "2ce56d130ddff67f43ec857cc51cd3
> 47666a0078"
> > +SRCREV_machine_edgerouter ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
> > +SRCREV_machine_beaglebone ?= "79414e2b0e0b7f5b86e358a907f841486f428079"
> > +SRCREV_machine_mpc8315e-rdb ?= "398d1785c6bde0085b99f00f346e19
> 9a15fbdcef"
> >
> >  COMPATIBLE_MACHINE_genericx86 = "genericx86"
> >  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> > --
> > 2.5.0
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] dllmap config for a Mono app

2017-06-08 Thread Craig McQueen
Joshua Watt wrote:
> On Thu, 2017-06-08 at 16:41 +1000, Craig McQueen wrote:
> > I have a Mono app that uses DllImport to load some functions from
> > libraries. The app can't find the libraries unless I create a Mono
> > config file containing dllmap lines to map the library's plain "DLL"
> > name (e.g. "foo") to the real name of the .so file (e.g.
> > "libfoo.so.4").
> 
> I'm not familiar with Mono, is libfoo a plain old library that anyone can 
> use, or
> it is some special "Mono Library"

It's a plain old library. It just so happens that I wrote it, but other than 
that it's a typical library.

> > * What would be a good way in the .bb recipe to automatically create
> > the required Mono config file? It would need to find the "real" names
> > of the library files from the library(s) build output. So it would
> > DEPENDS on the library(s).
> >
> > * Is it better to create a local config file, or write it into
> > /etc/mono/config? (My Mono app has the DllImports in a compiled DLL,
> > and so far I've found that I need to create a local MyDll.dll.config
> > file; making a MyApp.exe.config file doesn't work.)
> 
> Packaging rules require that every file belong to one and only one package. If
> your application writes /etc/mono/config, you wouldn't be able to write that
> file from any other package, including some other Mono application. The
> MyApp.exe.config file (unfortunately) sounds like the ideal solution, because
> you know that no other package is going to try and write that file. Writing
> MyDll.dll.config runs into the same problem as /etc/mono/config (at least if
> you are trying to write it from your MyApp recipe), as another app might
> want to write the same file because it uses the same library but that isn't
> allowed by the packaging rules. If you want to write MyDll.dll.config, it 
> should
> be done in the recipe that actually creates the dll.

/etc/mono/config is the "standard" system file for Mono, and an initial file is 
created by the mono recipe, so Mono can load various standard system libraries 
such as libc.so.6. Modifying it would be comparable to modifying other system 
config files such as /etc/modules, where it would be better to add a file to 
/etc/modprobe.d/. But unfortunately Mono doesn't provide for loading config 
from files in a directory like /etc/mono/config.d/

I guess I need to write to MyDll.dll.config in the recipe for my Mono app then.

Thanks for the advice on this, much appreciated.

-- 
Craig McQueen

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH] pacemaker: update to 1.1.16

2017-06-08 Thread jackie.huang
From: Jackie Huang 

* update the licenses and checksum
* fix PN -> BPN for multilib builds
* add PACKAGECONFIG for systemd and libsmtp
* add fix for libgnutls

Signed-off-by: Jackie Huang 
---
 ...006-pacemaker-do-not-use-libgnutls-config.patch | 29 ++
 .../{pacemaker_1.1.15.bb => pacemaker_1.1.16.bb}   | 22 +---
 2 files changed, 42 insertions(+), 9 deletions(-)
 create mode 100755 
meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0006-pacemaker-do-not-use-libgnutls-config.patch
 rename meta-cgl-common/recipes-cgl/pacemaker/{pacemaker_1.1.15.bb => 
pacemaker_1.1.16.bb} (84%)

diff --git 
a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0006-pacemaker-do-not-use-libgnutls-config.patch
 
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0006-pacemaker-do-not-use-libgnutls-config.patch
new file mode 100755
index 000..46e45df
--- /dev/null
+++ 
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0006-pacemaker-do-not-use-libgnutls-config.patch
@@ -0,0 +1,29 @@
+commit bb26b7c290473af988aa9d4132ef55ca907091e6
+Author: Joe Slater 
+Date:   Mon Mar 11 15:47:54 2013 -0700
+
+pacemaker: do not use libgnutls-config
+
+Do not try to use libgnutls-config when configuring.
+It has been deprecated and we do not supply it.  If a
+host version is found, bad things can happen.
+
+Signed-off-by: Joe Slater 
+Signed-off-by: Jackie Huang 
+
+
+--- a/configure.ac
 b/configure.ac
+@@ -1427,9 +1427,9 @@ dnl 
+ AC_CHECK_HEADERS(gnutls/gnutls.h)
+ AC_CHECK_HEADERS(security/pam_appl.h pam/pam_appl.h)
+ 
+-dnl GNUTLS library: Attempt to determine by 'libgnutls-config' program.
+-dnl If no 'libgnutls-config', try traditional autoconf means.
+-AC_PATH_PROGS(LIBGNUTLS_CONFIG, libgnutls-config)
++dnl libgnutls-config has been deprecated, so we use pkg-config
++
++LIBGNUTLS_CONFIG="pkg-config gnutls"
+ 
+ if test -n "$LIBGNUTLS_CONFIG"; then
+   AC_MSG_CHECKING(for gnutls header flags)
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb 
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.16.bb
similarity index 84%
rename from meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
rename to meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.16.bb
index 7dfbc26..cc1dd3d 100755
--- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.16.bb
@@ -8,29 +8,33 @@ when related resources fail and can be configured to 
periodically \
 check resource health."
 HOMEPAGE = "http://www.clusterlabs.org";
 
-LICENSE = "GPLv2+ & LGPLv2+"
-LIC_FILES_CHKSUM = "file://COPYING;md5=6adca3b36477cc77e04376f9a40df32c \
-file://COPYING.LIB;md5=243b725d71bb5df4a1e5920b344b86ad \
-   "
+LICENSE = "GPLv2+ & LGPLv2.1+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=19a64afd3a35d044a80579d7aafc30ff"
+
 DEPENDS = "corosync libxslt openais libxml2 gnutls resource-agents libqb 
python-native"
 
-SRC_URI = "https://github.com/ClusterLabs/${PN}/archive/Pacemaker-${PV}.zip \
+SRC_URI = "https://github.com/ClusterLabs/${BPN}/archive/Pacemaker-${PV}.zip \
file://0001-pacemaker-fix-xml-config.patch \

file://0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch \
file://0003-pacemaker-fix-header-defs-lookup.patch \
file://0004-pacemaker-do-not-build-help.patch \

file://0005-pacemaker-do-not-execute-target-program-while-cross-.patch \
+   file://0006-pacemaker-do-not-use-libgnutls-config.patch \
file://fix_missing_qb_array.patch \
file://volatiles \
file://tmpfiles \
   "
-SRC_URI[md5sum] = "def7902672872a6f43581b694eb34a4b"
-SRC_URI[sha256sum] = 
"0191037508b73a364c157892258bab72184384ebb854ff5233e84941fe014f5e"
+SRC_URI[md5sum] = "6f60f733823d31acbef4556fb749c457"
+SRC_URI[sha256sum] = 
"2642264b27c584eff5747a2a34c7f2bff13d52741e4e5cc70f14b2b6cd1fe7d5"
 
 inherit autotools-brokensep pkgconfig systemd python-dir useradd
 
 S="${WORKDIR}/pacemaker-Pacemaker-${PV}"
 
+PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}"
+PACKAGECONFIG[systemd] = "--enable-systemd,--disable-systemd,systemd"
+PACKAGECONFIG[libesmtp] = "--with-esmtp=yes,--with-esmtp=no,libesmtp"
+
 EXTRA_OECONF += "STAGING_INCDIR=${STAGING_INCDIR} \
  --disable-fatal-warnings \
  --with-ais \
@@ -41,9 +45,9 @@ EXTRA_OECONF += "STAGING_INCDIR=${STAGING_INCDIR} \
 do_install_append() {
 install -d ${D}${sysconfdir}/default
 install -d ${D}${sysconfdir}/default/volatiles
-install -m 0644 ${WORKDIR}/volatiles 
${D}${sysconfdir}/default/volatiles/06_${PN}
+install -m 0644 ${WORKDIR}/volatiles 
${D}${sysconfdir}/default/volatiles/06_${BPN}
 install -d ${D}${sysconfdir}/tmpfiles.d
-install -m 0644 ${WORKDIR}/tmpfiles ${D}${sysconfdir}/tmpfiles.d/${PN}.conf
+install -m 0644 ${WORKDIR}/tmpfiles 
${D}${sysconfdir}/t

[yocto] [meta-cgl][PATCH] crmsh: add new recipe

2017-06-08 Thread jackie.huang
From: Jackie Huang 

crm shell, a Pacemaker command line interface for
management and configuration.

Signed-off-by: Jackie Huang 
---
 .../recipes-cgl/crmsh/crmsh/tweaks_for_build.patch | 31 +
 meta-cgl-common/recipes-cgl/crmsh/crmsh_2.3.2.bb   | 32 ++
 2 files changed, 63 insertions(+)
 create mode 100644 
meta-cgl-common/recipes-cgl/crmsh/crmsh/tweaks_for_build.patch
 create mode 100644 meta-cgl-common/recipes-cgl/crmsh/crmsh_2.3.2.bb

diff --git a/meta-cgl-common/recipes-cgl/crmsh/crmsh/tweaks_for_build.patch 
b/meta-cgl-common/recipes-cgl/crmsh/crmsh/tweaks_for_build.patch
new file mode 100644
index 000..6e1a291
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/crmsh/crmsh/tweaks_for_build.patch
@@ -0,0 +1,31 @@
+Upstream-Status: Inappropriate [embedded specific]
+
+Pass option '--catalogs' to xsltproc via a2x to avoid network access.
+And disble xmllint check by option '-L'.
+
+Add option '--install-lib' of python setup.py to install python libraries to
+right place.
+
+Signed-off-by: Kai Kang 
+---
+diff --git a/Makefile.am b/Makefile.am
+index d89affb..0f2361f 100644
+--- a/Makefile.am
 b/Makefile.am
+@@ -47,7 +47,7 @@ endif
+   $(ASCIIDOC) --unsafe --backend=xhtml11 $<
+ 
+ %.8: %.8.adoc
+-  a2x -f manpage $<
++  a2x --xsltproc-opts=--catalogs -L -f manpage $<
+ 
+ # Shared data files
+ install-data-hook:
+@@ -79,6 +79,7 @@ install-exec-local:
+   -mkdir -p $(DESTDIR)$(pkgpythondir)
+   $(PYTHON) $(srcdir)/setup.py install \
+   $(python_prefix) \
++  --install-lib $(pythondir) \
+   --record $(DESTDIR)$(pkgpythondir)/install_files.txt \
+   --verbose
+   $(INSTALL) -d -m 770 $(DESTDIR)/$(CRM_CACHE_DIR)
diff --git a/meta-cgl-common/recipes-cgl/crmsh/crmsh_2.3.2.bb 
b/meta-cgl-common/recipes-cgl/crmsh/crmsh_2.3.2.bb
new file mode 100644
index 000..709fbff
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/crmsh/crmsh_2.3.2.bb
@@ -0,0 +1,32 @@
+SUMMARY = "Pacemaker command line interface for management and configuration"
+DESCRIPTION = "crm shell, a Pacemaker command line interface for management 
and configuration"
+
+HOMEPAGE = "https://crmsh.github.io";
+
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
+
+DEPENDS = "asciidoc-native \
+   docbook-xsl-stylesheets-native \
+   libxslt-native \
+   python-setuptools-native \
+   "
+RDEPENDS_${PN} = "pacemaker python-lxml gawk"
+
+SRC_URI = 
"https://github.com/ClusterLabs/crmsh/archive/${PV}.tar.gz;downloadfilename=${BP}.tar.gz
 \
+   file://tweaks_for_build.patch \
+  "
+
+SRC_URI[md5sum] = "0a475d3c56a158dc991de61a26450eb5"
+SRC_URI[sha256sum] = 
"ac78b7786f6a52cc3d86b3d80b2d8627e84873330cd4846d5ea48869189ad864"
+
+inherit autotools-brokensep distutils-base
+
+export HOST_SYS
+export BUILD_SYS
+
+# Allow to process DocBook documentations without requiring
+# network accesses for the dtd and stylesheets
+export SGML_CATALOG_FILES = 
"${STAGING_DATADIR_NATIVE}/xml/docbook/xsl-stylesheets/catalog.xml"
+
+FILES_${PN} += "${PYTHON_SITEPACKAGES_DIR}/${BPN}"
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH] racoon2: add new recipe

2017-06-08 Thread yi.zhao
From: Yi Zhao 

The Racoon2 project is a joint effort which provides an implementation
of key management system for IPsec. It supports IKEv1, IKEv2, and KINK
protocols.

Signed-off-by: Yi Zhao 
---
 .../recipes-cgl/racoon2/racoon2/iked.service   |  14 +
 .../racoon2-Add-Value-to-HAVE_NSSWITCH_CONF.patch  |  32 +++
 .../racoon2/racoon2/racoon2-DESTDIR.patch  | 202 +++
 .../racoon2/racoon2-Remove-INSTALL_OPTS.patch  |  87 +++
 .../racoon2/racoon2-configure-autoheader.patch |  60 +
 .../racoon2/racoon2/racoon2-configure-memcmp.patch |  32 +++
 ...oon2-configure.in-remove-redundant-macros.patch | 199 +++
 .../racoon2-correct-openssl-include-path.patch |  70 +
 .../racoon2/racoon2-disable-hard-limit-timer.patch |  80 ++
 .../racoon2/racoon2-fix-configure-error.patch  |  50 
 .../racoon2/racoon2-fix-hardcoded-sysconfdir.patch | 281 +
 .../racoon2/racoon2-fix-rekeying-reply.patch   |  28 ++
 .../racoon2-fix-sadb_msg_seq-collision.patch   |  41 +++
 ...oon2-fix-target-perl-path-to-generate-RPM.patch |  86 +++
 .../racoon2/racoon2-fwrite-return-value.patch  |  34 +++
 .../racoon2/racoon2/racoon2-iked-initscript.patch  |  34 +++
 .../racoon2/racoon2-iked-needs-libcrypto.patch |  34 +++
 .../racoon2/racoon2/racoon2-kinkd-initscript.patch |  34 +++
 .../racoon2/racoon2-reenable-the-ipv6-check.patch  |  65 +
 .../racoon2-remove-deprecated-do-clause.patch  |  19 ++
 .../racoon2-removed-conflicting-prototypes.patch   |  51 
 .../racoon2/racoon2/racoon2-spmd-initscript.patch  |  33 +++
 .../recipes-cgl/racoon2/racoon2/spmd.service   |  12 +
 .../racoon2/racoon2/volatiles.99_racoon2   |   1 +
 .../recipes-cgl/racoon2/racoon2_20100526a.bb   | 104 
 25 files changed, 1683 insertions(+)
 create mode 100644 meta-cgl-common/recipes-cgl/racoon2/racoon2/iked.service
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-Add-Value-to-HAVE_NSSWITCH_CONF.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-DESTDIR.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-Remove-INSTALL_OPTS.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-configure-autoheader.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-configure-memcmp.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-configure.in-remove-redundant-macros.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-correct-openssl-include-path.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-disable-hard-limit-timer.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-fix-configure-error.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-fix-hardcoded-sysconfdir.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-fix-rekeying-reply.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-fix-sadb_msg_seq-collision.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-fix-target-perl-path-to-generate-RPM.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-fwrite-return-value.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-iked-initscript.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-iked-needs-libcrypto.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-kinkd-initscript.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-reenable-the-ipv6-check.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-remove-deprecated-do-clause.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-removed-conflicting-prototypes.patch
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-spmd-initscript.patch
 create mode 100644 meta-cgl-common/recipes-cgl/racoon2/racoon2/spmd.service
 create mode 100644 
meta-cgl-common/recipes-cgl/racoon2/racoon2/volatiles.99_racoon2
 create mode 100644 meta-cgl-common/recipes-cgl/racoon2/racoon2_20100526a.bb

diff --git a/meta-cgl-common/recipes-cgl/racoon2/racoon2/iked.service 
b/meta-cgl-common/recipes-cgl/racoon2/racoon2/iked.service
new file mode 100644
index 000..3ec4f96
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/racoon2/racoon2/iked.service
@@ -0,0 +1,14 @@
+[Unit]
+Description=daemon for the Internet Key Exchange
+After=syslog.target network.target spmd.service
+Requires=spmd.service
+
+[Service]
+Type=forking
+PIDFile=/var/run/iked.pid
+ExecStart=@SBINDIR@/iked
+ExecReload=@BASE_BINDIR@/kill -HUP $MAINPID
+SuccessExitStatus=1
+
+[Install]
+WantedBy=multi-user.target
diff --git 
a/meta-cgl-common/recipes-cgl/racoon2/racoon2/racoon2-Add-Value-to-HAVE_NSSWITCH_CONF.patch

Re: [yocto] [PATCH V3 00/11] Several fixes for layerindex

2017-06-08 Thread Robert Yang

Hi Paul,

I updated the following patch a little:

[PATCH V3 06/11] update.py: update layers orderly

Checkout the branch before parse layer:

+if not options.nocheckout:
+utils.checkout_layer_branch(layerbranch, repodir, logger=logger)

Updated in the repo:
  git://git.pokylinux.org/poky-contrib rbt/layerindex-8fixes
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=rbt/layerindex-8fixes

Robert Yang (11):
  layerconfparse.py: remove unused layerbranch from parse_layer()
  utils.py: remove obsolete dependencies
  update_layer.py: set layerbranch's collection before add_dependencies
  update.py: fix -l option
  recipeparse.py: restore cwd when the parsing is done
  update.py: update layers orderly
  update_layer.py: remove --update-dependencies
  update.py: add option -a to update actual branch
  update_layer.py: move the location of transaction.atomic()
  update.py: add -p to git fetch
  update_layer.py: delete layerbranch for non-existed branch

// Robert

On 06/02/2017 02:28 PM, Robert Yang wrote:

* V3:
  - Better error messages when required collections not found
  - Delete layerbranch for non-existed branch
  - update_layer.py: remove --update-dependencies

* V2:
  - Remove "import bb" from update.py to avoid causing confusions when switch 
branches.

* V1:
  - The "-a ACTUAL_BRANCH" is a litle different from what we had talked, now it
respects "-l" and "-b", we can use -l to specify layers or default to all,
and it requires "-b" to work, only one branch is supported in a run, for 
example:

$ update.py -b master -a branch_20170526
All the layers which have branch master and actual_branch branch_20170526
will be updated to branch_20170526.

$ update.py -b master -l meta-oe -a branch_20170526
Only meta-oe layer will be updated.

$ update.py -b master -l bitbake -a branch_20170526
The bitbake's bitbake_branch will be updated.

// Robert

The following changes since commit 8dfe44ed5e618d517d4acb4a3107cb3907e773c8:

  TODO: drop implemented items (2017-03-22 14:21:22 +1300)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib rbt/layerindex-8fixes
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=rbt/layerindex-8fixes

Robert Yang (11):
  layerconfparse.py: remove unused layerbranch from parse_layer()
  utils.py: remove obsolete dependencies
  update_layer.py: set layerbranch's collection before add_dependencies
  update.py: fix -l option
  recipeparse.py: restore cwd when the parsing is done
  update.py: update layers orderly
  update_layer.py: remove --update-dependencies
  update.py: add option -a to update actual branch
  update_layer.py: move the location of transaction.atomic()
  update.py: add -p to git fetch
  update_layer.py: delete layerbranch for non-existed branch

 layerindex/layerconfparse.py |   2 +-
 layerindex/recipeparse.py|   3 +
 layerindex/tools/import_layer.py |   2 +-
 layerindex/update.py | 193 +++
 layerindex/update_layer.py   |  92 +++
 layerindex/utils.py  |  63 -
 6 files changed, 255 insertions(+), 100 deletions(-)


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto