Re: [yocto] License missing coreutils when creating /usr/share/licenses and bbappend

2017-07-11 Thread Dr . Matthias Schöpfer 
Hi Khem,



i.A. Dr.-Ing. Matthias  Schöpfer  | ithinx GmbH |  Software Engineer
Phone:  +49 (221) 99589-332 | Fax: +49 (221) 99 589-199  | E-Mail:  
matthias.schoep...@ithinx.io


On 07/10/2017 07:27 PM, Khem Raj wrote:
> On 7/10/17 9:19 AM, Dr. Matthias Schöpfer wrote:
>> Hi!
>>
>> We are using yocto / openembedded (pyro). I use:
>>
>> COPY_LIC_MANIFEST = "1"
>> COPY_LIC_DIRS = "1"
>> LICENSE_CREATE_PACKAGE = "1"
>>
>> to generate a /usr/share/licenses and /usr/share/common-licenses
>> respectively. But unfortunately, the coreutils subdirectory is empty.
>>
>> I use a bbappend file containing only:
>>
>> ALTERNATIVE_PRIORITY = "40"
>> ALTERNATIVE_PRIORITY[od] = "100"
>>
>> such that only od gets installed (remaining functionality by busybox).
>>
>> Any hints on how to get the license info in there as well?!
> you might have to check if od is getting installed from coreutils or
> some other package is providing it.

I can confirm that definitely od.coreutils is installed. That works. But
still, License is missing :(

Regards,

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

Re: [yocto] [yocto-autobuilder][PATCH] ScrapeTargets.py: Use python instead of awk

2017-07-11 Thread Joshua Lock 
On Mon, 2017-07-10 at 14:05 -0700, Stephano Cetola wrote:
> Using awk, sed, or grep to pull a shell variable out of stdio proved
> complex. Instead, simply cat the entire "inc" file to stdio and use
> python/regex to find the variable.

Merged, thanks!

> Signed-off-by: Stephano Cetola 
> ---
>  .../autobuilder/buildsteps/ScrapeTargets.py | 17
> ++---
>  1 file changed, 10 insertions(+), 7 deletions(-)
> 
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/ScrapeTargets.py
> b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
> index 07e2fdcf4..8844c6366 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/ScrapeTargets.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/ScrapeTargets.py
> @@ -15,6 +15,7 @@ from buildbot.steps.shell import ShellCommand
>  from buildbot.status.results import SUCCESS, FAILURE
>  from autobuilder.config import *
>  import os
> +import re
>  
>  class ScrapeTargets(ShellCommand):
>  haltOnFailure = False
> @@ -41,9 +42,7 @@ class ScrapeTargets(ShellCommand):
>  workerdir = os.path.join(os.path.join(YOCTO_ABBASE, "yocto-
> worker"))
>  buildername = self.getProperty("buildername")
>  src = os.path.join(workerdir, buildername, "build",
> self.source)
> -# find targetsvar then return lines up to a quote
> -self.command = ["awk",
> -'/%s/{flag=1;print;next}/"/{flag=0}flag' %
> self.targetsvar, src]
> +self.command = ["cat", src]
>  ShellCommand.start(self)
>  
>  def commandComplete(self, cmd):
> @@ -51,10 +50,14 @@ class ScrapeTargets(ShellCommand):
>  return
>  
>  result = cmd.logs['stdio'].getText()
> -targets = result.strip()
> -targets = targets.replace('%s="' % self.targetsvar, '')
> -targets = targets.replace('\\', '')
> -targets = targets.replace('\n', '')
> +start = result.find(self.targetsvar) + len(self.targetsvar)
> +res = re.search('"([^"]*)"', result[start:])
> +targets = ""
> +if res:
> +targets = res.group()
> +targets = targets.replace('%s="' % self.targetsvar, '')
> +targets = targets.replace('\\', '')
> +targets = targets.replace('\n', '')
>  self.setProperty("scraped_targets",
>   targets,
>   'Targets "%s" scraped from %s' % (targets,
> -- 
> 2.13.2
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-autobuilder][PATCH] add force bash option on build and preamble

2017-07-11 Thread Joshua Lock 
On Mon, 2017-07-10 at 14:04 -0700, Stephano Cetola wrote:
> Certain distros (Ubuntu) use a less desirable shell for /bin/sh
> (dash). In some edge cases, if we source oe-init-build-env from
> outside the OEROOT folder, the script will fail (as stated in the
> oe-init-build-env script). By adding a variable to force bash as the
> shell, we can call "bash -c" to ensure that a compatible shell is
> used.
> 
> Currently, refkit is the only build that suffers from this edge case.

Thanks for the fix! I split the patch into two before merging, one for
the buildstep logic change and a follow-on to update the buildset-
config.controller. Hope you don't mind.

Joshua

> Signed-off-by: Stephano Cetola 
> ---
>  buildset-config.controller/nightly-refkit.conf|
> 3 ++-
>  lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py |
> 3 +++
>  lib/python2.7/site-packages/autobuilder/buildsteps/RunPreamble.py |
> 3 +++
>  3 files changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/buildset-config.controller/nightly-refkit.conf
> b/buildset-config.controller/nightly-refkit.conf
> index 1d2487da6..cbc8508d7 100644
> --- a/buildset-config.controller/nightly-refkit.conf
> +++ b/buildset-config.controller/nightly-refkit.conf
> @@ -11,7 +11,7 @@ repos: [{'poky':
>   'submodules': True}}]
>  steps: [{'SetDest':{}},
>  {'CheckOutLayers': {'submodules': True}},
> -{'RunPreamble': {'altcmd': 'refkit/oe-init-build-env'}},
> +{'RunPreamble': {'forcebash': True, 'altcmd': 'refkit/oe-
> init-build-env'}},
>  {'GetDistroVersion' : {'distro': 'refkit'}},
>  {'CreateAutoConf': {'machine': 'intel-corei7-64',
> 'packages': 'ipk',
>  'distro': 'refkit', 'buildhistory' :
> False,
> @@ -44,6 +44,7 @@ steps: [{'SetDest':{}},
>  {'ScrapeTargets': {'source': 'refkit/meta-
> refkit/conf/distro/include/refkit-ci.inc',
> 'targetsvar':
> 'REFKIT_CI_BUILD_TARGETS'}},
>  {'BuildImages': {'images': '#SCRAPEDTARGETS',
> + 'forcebash': True,
>   'oeinit': 'refkit/oe-init-build-env',
>   'overrideenv':
> ['BITBAKEDIR=#YPDIR/bitbake', 'OEROOT=#YPDIR/meta']}},
>  {'ScrapeTargets': {'source': 'refkit/meta-
> refkit/conf/distro/include/refkit-ci.inc',
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/BuildImages.py b/lib/python2.7/site-
> packages/autobuilder/buildsteps/BuildImages.py
> index 60ce07ff7..0406fd2e9 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/BuildImages.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/BuildImages.py
> @@ -23,6 +23,7 @@ class BuildImages(BitbakeShellCommand):
>  haltOnFailure = False
>  flunkOnFailure = True
>  name = "BuildImages"
> +forcebash = False
>  def __init__(self, factory, argdict=None, **kwargs):
>  self.layerversion_yoctobsp=0
>  self.machine=""
> @@ -163,6 +164,8 @@ class BuildImages(BitbakeShellCommand):
>  if self.minnowExists is None or self.minnowExists ==
> "True":
>  self.command = env + ". ./" + self.oeinit + ";
> bitbake " + bitbakeflags + self.images
>  self.description = ["Building " +
> str(self.images)]
> +if self.forcebash:
> +self.command = ['bash', '-c', self.command]
>  ShellCommand.start(self)
>  
>  def describe(self, done=False):
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/RunPreamble.py b/lib/python2.7/site-
> packages/autobuilder/buildsteps/RunPreamble.py
> index e9de3c76c..23c4ace2b 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/RunPreamble.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/RunPreamble.py
> @@ -16,6 +16,7 @@ class RunPreamble(ShellCommand):
>  haltOnFailure = False
>  flunkOnFailure = True
>  name = "RunPreamble"
> +forcebash = False
>  
>  def __init__(self, factory, argdict=None, **kwargs):
>  self.factory = factory
> @@ -27,4 +28,6 @@ class RunPreamble(ShellCommand):
>  self.command = ". ./oe-init-build-env"
>  else:
>  self.command = ". ./" + self.altcmd
> +if self.forcebash:
> +self.command = ['bash', '-c', self.command]
>  ShellCommand.__init__(self, **kwargs)
> -- 
> 2.13.2
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] apparmor: Additional runtime fixes

2017-07-11 Thread Tom Rini 
- We need various python3 modules and we can only really solve this
  problem by including all python3-modules.
- aa-easyprof needs to have its shebang corrected, do so.
- The apparmor initscript depends on functions that LSB does not require
  so we must provide them.  In some cases it's using non-standard
  function, so we just use more appropriate names.
- The apparmor sysvinit-style initscript assumes that
  systemd-detect-virt will exist on the filesystem.  Change this to
  check that it does before trying to execute it.

[for aa-easyprof:]
Reported-by: Anders Montonen 
Signed-off-by: Tom Rini 
---
 recipes-security/AppArmor/apparmor_2.11.0.bb |  6 +-
 recipes-security/AppArmor/files/apparmor | 30 +---
 2 files changed, 28 insertions(+), 8 deletions(-)

diff --git a/recipes-security/AppArmor/apparmor_2.11.0.bb 
b/recipes-security/AppArmor/apparmor_2.11.0.bb
index 647ab124f115..d9572e4e626f 100644
--- a/recipes-security/AppArmor/apparmor_2.11.0.bb
+++ b/recipes-security/AppArmor/apparmor_2.11.0.bb
@@ -79,6 +79,10 @@ do_install () {
oe_runmake -C ${B}/changehat/pam_apparmor DESTDIR="${D}" install
fi
 
+   # aa-easyprof is installed by python-tools-setup.py, fix it up
+   sed -i -e 's:/usr/bin/env.*:/usr/bin/python3:' ${D}${bindir}/aa-easyprof
+   chmod 0755 ${D}${bindir}/aa-easyprof
+
install ${WORKDIR}/apparmor ${D}/${INIT_D_DIR}/apparmor
install ${WORKDIR}/functions ${D}/lib/apparmor
 }
@@ -124,6 +128,6 @@ FILES_${PN} += "/lib/apparmor/ ${sysconfdir}/apparmor 
${PYTHON_SITEPACKAGES_DIR}
 FILES_mod-${PN} = "${libdir}/apache2/modules/*"
 
 RDEPENDS_${PN} += "bash lsb"
-RDEPENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG','python','python3 
python3-argparse python3-json','', d)}"
+RDEPENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG','python','python3 
python3-modules','', d)}"
 RDEPENDS_${PN}_remove += 
"${@bb.utils.contains('PACKAGECONFIG','perl','','perl', d)}"
 RDEPENDS_${PN}-ptest += "coreutils dbus-lib"
diff --git a/recipes-security/AppArmor/files/apparmor 
b/recipes-security/AppArmor/files/apparmor
index c73c1cec94e9..ac3ab9a4acb5 100644
--- a/recipes-security/AppArmor/files/apparmor
+++ b/recipes-security/AppArmor/files/apparmor
@@ -32,6 +32,20 @@
 # Description: AppArmor init script. This script loads all AppArmor profiles.
 ### END INIT INFO
 
+log_daemon_msg() {
+echo $*
+}
+
+log_end_msg () {
+retval=$1
+if [ $retval -eq 0 ]; then
+echo "."
+else
+echo " failed!"
+fi
+return $retval
+}
+
 . /lib/apparmor/functions
 . /lib/lsb/init-functions
 
@@ -47,20 +61,19 @@ securityfs() {
# Need securityfs for any mode
if [ ! -d "${AA_SFS}" ]; then
if cut -d" " -f2,3 /proc/mounts | grep -q "^${SECURITYFS} 
securityfs"'$' ; then
-   log_action_msg "AppArmor not available as kernel LSM."
+   log_daemon_msg "AppArmor not available as kernel LSM."
log_end_msg 1
exit 1
else
-   log_action_begin_msg "Mounting securityfs on 
${SECURITYFS}"
+   log_daemon_msg "Mounting securityfs on ${SECURITYFS}"
if ! mount -t securityfs none "${SECURITYFS}"; then
-   log_action_end_msg 1
log_end_msg 1
exit 1
fi
fi
fi
if [ ! -w "$AA_SFS"/.load ]; then
-   log_action_msg "Insufficient privileges to change profiles."
+   log_daemon_msg "Insufficient privileges to change profiles."
log_end_msg 1
exit 1
fi
@@ -127,7 +140,8 @@ test -d /rofs/etc/apparmor.d && exit 0
 rc=255
 case "$1" in
start)
-   if systemd-detect-virt --quiet --container && \
+   if test -x /sbin/systemd-detect-virt && \
+  systemd-detect-virt --quiet --container && \
   ! is_container_with_internal_policy; then
log_daemon_msg "Not starting AppArmor in container"
log_end_msg 0
@@ -161,7 +175,8 @@ with the 'teardown' option."
 EOM
;;
teardown)
-   if systemd-detect-virt --quiet --container && \
+   if test -x /sbin/systemd-detect-virt && \
+  systemd-detect-virt --quiet --container && \
   ! is_container_with_internal_policy; then
log_daemon_msg "Not tearing down AppArmor in container"
log_end_msg 0
@@ -179,7 +194,8 @@ EOM
log_end_msg $rc
;;
restart|reload|force-reload)
-   if systemd-detect-virt --quiet --container && \
+   if test -x /sbin/systemd-detect-virt && \
+  systemd-detect-virt --quiet --container && \

[yocto] Minutes: Yocto Project Technical Team Meeting

2017-07-11 Thread Jolley, Stephen K 
Attendees: Saul, Stephen, Joshua L., Richard, Paul, Stephano, Joshua W., Ross, 
Libby, Trevor, Christopher,

Agenda:

* Opens collection - 5 min (Stephen)
* Yocto Project status - 5 min (Stephen/team)
YP 2.4 M1 has been released
YP 2.1.3 has been released
YP 2.3.1 and YP 2.2.2 are still planned, but not yet ready to be built.
YP 2.4 M2 is planned to be built next week.

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.4_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.4_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.4_Features

* Opens - 10 min

https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance

* Team Sharing - 10 min
Richard - Continuing on with the project.  GCC upgrades and tools hardening.  
Still debating Memory Resident Bitbake to be default in M2.
Paul - Discussed that no one has complained about Memres yet, but have people 
been testing it?  Discussed the pro's and con's of using Memres.

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone: (503) 712-0534
*Cell:  (208) 244-4460
* Email:stephen.k.jolley@intel.comYP

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

[yocto] [qa-tools][PATCH] qa-tools: Modified current supported distributions for OE-Core testing

2017-07-11 Thread libertad . cruz 
From: Libertad Cruz 

Added OpenSuse 42.3, Fedora 26 and Ubuntu 17.04 distributions.
Removed unsupported distribution OpenSuse 13.2, Ubuntu 16.10.

Signed-off-by: Libertad Cruz 
---
 scripts/full-test-cycle-wrapper.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/full-test-cycle-wrapper.sh 
b/scripts/full-test-cycle-wrapper.sh
index 6b62d7f..23b8f57 100755
--- a/scripts/full-test-cycle-wrapper.sh
+++ b/scripts/full-test-cycle-wrapper.sh
@@ -197,8 +197,8 @@ create_test_cycle(){
   ;;
 "OE-Core")
   ENVIRONMENTS=("CentOS 7.1 x86_64" "Debian 8 x86_64" 
"Fedora 25 x86_64" "Fedora 24 x86_64" \
-   "OpenSuse 13.2 x86_64" "OpenSuse421 x86_64" 
"ubuntu 16.04 x86_64" \
-   "Ubuntu 16.10 x86-64")
+   "OpenSuse 42.3 x86_64" "OpenSuse421 x86_64" 
"ubuntu 16.04 x86_64" \
+   "Ubuntu 17.04 x86-64" "Fedora 26 x86_64" )
   EXECUTION_TYPE="AUTO"
   create_test_run "${1}"
   ;;
-- 
2.1.4

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

[yocto] [meta-alexa-demo][PATCH] Fix setuptools_scm build error for several python packages

2017-07-11 Thread Tim Orling 
python-setuptools-scm-native is needed at build time for:
  python-cheroot
  python-cherrypy
  python-portend
  python-tempora

Signed-off-by: Tim Orling 
---
 recipes-devtools/python/python-cheroot_5.1.0.bb   | 2 +-
 recipes-devtools/python/python-cherrypy_10.1.1.bb | 2 +-
 recipes-devtools/python/python-portend_1.8.bb | 2 +-
 recipes-devtools/python/python-tempora_1.6.1.bb   | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/recipes-devtools/python/python-cheroot_5.1.0.bb 
b/recipes-devtools/python/python-cheroot_5.1.0.bb
index 2da3115..e8795d1 100644
--- a/recipes-devtools/python/python-cheroot_5.1.0.bb
+++ b/recipes-devtools/python/python-cheroot_5.1.0.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/cheroot"
 
 BBCLASSEXTEND = "nativesdk"
 
-DEPENDS += " swig-native"
+DEPENDS += " swig-native python-setuptools-scm-native"
 
 RDEPENDS_${PN} += " \
 python-pip \
diff --git a/recipes-devtools/python/python-cherrypy_10.1.1.bb 
b/recipes-devtools/python/python-cherrypy_10.1.1.bb
index 2a75fd8..6a9086a 100644
--- a/recipes-devtools/python/python-cherrypy_10.1.1.bb
+++ b/recipes-devtools/python/python-cherrypy_10.1.1.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/CherryPy"
 
 BBCLASSEXTEND = "nativesdk"
 
-DEPENDS += " swig-native"
+DEPENDS += " swig-native python-setuptools-scm-native"
 
 RDEPENDS_${PN} += " \
 python-pip \
diff --git a/recipes-devtools/python/python-portend_1.8.bb 
b/recipes-devtools/python/python-portend_1.8.bb
index f50de7c..926d238 100644
--- a/recipes-devtools/python/python-portend_1.8.bb
+++ b/recipes-devtools/python/python-portend_1.8.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/portend"
 
 BBCLASSEXTEND = "nativesdk"
 
-DEPENDS += " swig-native"
+DEPENDS += " swig-native python-setuptools-scm-native"
 
 RDEPENDS_${PN} += " \
 python-pip \
diff --git a/recipes-devtools/python/python-tempora_1.6.1.bb 
b/recipes-devtools/python/python-tempora_1.6.1.bb
index 417818b..4412030 100644
--- a/recipes-devtools/python/python-tempora_1.6.1.bb
+++ b/recipes-devtools/python/python-tempora_1.6.1.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/tempora"
 
 BBCLASSEXTEND = "nativesdk"
 
-DEPENDS += " swig-native"
+DEPENDS += " swig-native python-setuptools-scm-native"
 
 RDEPENDS_${PN} += " \
 python-pip \
-- 
2.9.4

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

Re: [yocto] [meta-alexa-demo][PATCH] Fix setuptools_scm build error for several python packages

2017-07-11 Thread Cal Sullivan 
I actually wasn't able to reproduce the issue.I added alexapi to my 
IMAGE_INSTALL and ran a build, see below:


[clsulliv@clsulliv build]$ bitbake core-image-minimal
Parsing recipes: 100% 
|| 
Time: 0:00:08
Parsing of 1825 .bb files complete (0 cached, 1825 parsed). 2581 
targets, 143 skipped, 0 masked, 0 errors.

NOTE: There are 4 recipes to be removed from sysroot x86_64, removing...
NOTE: There are 1 recipes to be removed from sysroot corei7-64, removing...
NOTE: There are 1 recipes to be removed from sysroot intel-corei7-64, 
removing...

NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.34.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "x86_64-poky-linux"
MACHINE   = "intel-corei7-64"
DISTRO= "poky"
DISTRO_VERSION= "2.3"
TUNE_FEATURES = "m64 corei7"
TARGET_FPU= ""
meta
meta-poky
meta-yocto-bsp= "pyro:7c27bf2dd85ee77d643d975add4256e957652a5c"
meta-intel= "pyro:16aea09d224f3ed2021623d17c3e807f4b8ff18d"
meta-oe   = "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
meta-alexa= "master:1b5618a1af6ea79f51aa89480b857648584c581f"
meta-python
meta-multimedia   = "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"

Initialising tasks: 100% 
|#| 
Time: 0:00:11
Checking sstate mirror object availability: 100% 
|#| 
Time: 0:00:00

NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 5678 tasks of which 5653 didn't need to 
be rerun and all succeeded.


I'm curious as to what's different for you guys.

---
Cal


On 07/11/2017 02:25 PM, Tim Orling wrote:

python-setuptools-scm-native is needed at build time for:
   python-cheroot
   python-cherrypy
   python-portend
   python-tempora

Signed-off-by: Tim Orling 
---
  recipes-devtools/python/python-cheroot_5.1.0.bb   | 2 +-
  recipes-devtools/python/python-cherrypy_10.1.1.bb | 2 +-
  recipes-devtools/python/python-portend_1.8.bb | 2 +-
  recipes-devtools/python/python-tempora_1.6.1.bb   | 2 +-
  4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/recipes-devtools/python/python-cheroot_5.1.0.bb 
b/recipes-devtools/python/python-cheroot_5.1.0.bb
index 2da3115..e8795d1 100644
--- a/recipes-devtools/python/python-cheroot_5.1.0.bb
+++ b/recipes-devtools/python/python-cheroot_5.1.0.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/cheroot"
  
  BBCLASSEXTEND = "nativesdk"
  
-DEPENDS += " swig-native"

+DEPENDS += " swig-native python-setuptools-scm-native"
  
  RDEPENDS_${PN} += " \

  python-pip \
diff --git a/recipes-devtools/python/python-cherrypy_10.1.1.bb 
b/recipes-devtools/python/python-cherrypy_10.1.1.bb
index 2a75fd8..6a9086a 100644
--- a/recipes-devtools/python/python-cherrypy_10.1.1.bb
+++ b/recipes-devtools/python/python-cherrypy_10.1.1.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/CherryPy"
  
  BBCLASSEXTEND = "nativesdk"
  
-DEPENDS += " swig-native"

+DEPENDS += " swig-native python-setuptools-scm-native"
  
  RDEPENDS_${PN} += " \

  python-pip \
diff --git a/recipes-devtools/python/python-portend_1.8.bb 
b/recipes-devtools/python/python-portend_1.8.bb
index f50de7c..926d238 100644
--- a/recipes-devtools/python/python-portend_1.8.bb
+++ b/recipes-devtools/python/python-portend_1.8.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/portend"
  
  BBCLASSEXTEND = "nativesdk"
  
-DEPENDS += " swig-native"

+DEPENDS += " swig-native python-setuptools-scm-native"
  
  RDEPENDS_${PN} += " \

  python-pip \
diff --git a/recipes-devtools/python/python-tempora_1.6.1.bb 
b/recipes-devtools/python/python-tempora_1.6.1.bb
index 417818b..4412030 100644
--- a/recipes-devtools/python/python-tempora_1.6.1.bb
+++ b/recipes-devtools/python/python-tempora_1.6.1.bb
@@ -14,7 +14,7 @@ FILES_${PN} += "${datadir}/tempora"
  
  BBCLASSEXTEND = "nativesdk"
  
-DEPENDS += " swig-native"

+DEPENDS += " swig-native python-setuptools-scm-native"
  
  RDEPENDS_${PN} += " \

  python-pip \


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

[yocto] Determining Load Addresses

2017-07-11 Thread Kenny Koller 
I'm trying to piece together the various load addresses used in the boot
sequence. I have built core-image-minimal for a Beaglebone. How can I
determine which load address and entry point is used when mkimage is called
for the kernel? Should I dig in to the recipe? Search some log files? I've
tried a few difference things without results.

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