date:20160527

Re: [yocto] On target gdb support for multiple architectures?

2016-05-27 Thread Khem Raj

There should be two gdb executables on your target.
On May 26, 2016 3:34 PM, "Stroz, Glenn"  wrote:

> Hello,
>
>
>
> We’re trying to setup our target for onboard debugging. We have multiple
> architectures being built with multilib. An armv7 variant which is 32 bit
> and an armv8 variant which is 64 bit. We would like the gdb installed in
> the image to support both architectures. Right now, even when adding both
> gdb and lib32-gdb to the image we see it only supports aarch64.
>
>
>
> #
>
> # Multilib configuration
>
> #
>
> # This sets any packages preprended with lib32- to be built with
>
> # the armv7a tuning (32 bit) instead of 64 bit aarch.
>
> #
>
> require conf/multilib.conf
>
> MULTILIBS = "multilib:lib32"
>
> DEFAULTTUNE_virtclass-multilib-lib32 = "armv7a-neon"
>
>
>
> When adding lib32-gdb and gdb to image:
>
> (gdb) set architecture
>
> Requires an argument. Valid arguments are aarch64, aarch64:ilp32, auto.
>
>
>
> When adding only lib32-gdb to image:
>
> (gdb) set architecture
>
> Requires an argument. Valid arguments are arm, armv2, armv2a, armv3,
> armv3m, armv4, armv4t, armv5, armv5t, armv5te, xscale, ep9312, iwmmxt,
> iwmmxt2, auto.
>
>
>
> Is there any method of getting the build system to combine the two lists
> of architectures into one binary that supports them all?
>
>
>
> Thanks,
>
> Glenn
>
> --
> ___
> 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] Systemd-udevd cache

2016-05-27 Thread Stefano Cordibella


Hi list,
I am moving a distro form sysvinit to systemd (based on jethro), 
but I can't find informations about udev cache in systemd...
I see that the udev cache in sysvinit is managed by an external script, 
but in systemd?


Any help on how to use a device cache or static node creation will be 
appreciated.


Thank you for your time,
Stefano.

--
*Stefano Cordibella*
EDALab s.r.l. - Networked Embedded Systems

Strada Le Grazie, 15 - 37134 Verona - Italy
email : stefano.cordibe...@edalab.it
skype : stefano.cordibella
tel. : +39 045 802 70 85
web : www.edalab.it
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][matchbox-wm] wm: Do not set MB theme based on Net/ThemeName

2016-05-27 Thread Burton, Ross

On 26 April 2016 at 08:57, Jussi Kukkonen  wrote:

> MBWM already supports setting MB theme with "MATCHBOX/THEME",
> there is no advantage to also set it with "Net/ThemeName" -- the
> expectation that MBWM has a matching theme for all toolkit themes
> is not realistic.
>
> Net/ThemeName is used by Gtk+ to set Gtk theme so this change allows
> the Gtk theme and MBWM theme to have different names.
>

This behaviour is useful though, how about supporting both but having
Matchbox/Theme override Net/ThemeName?

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

[yocto] Yocto Project Status WW22

2016-05-27 Thread Jolley, Stephen K

Current Dev Position: YP 2.2 M1

Next Deadline: YP 2.2 cut off: June 13, 2016


SWAT team rotation: Tracy -> Alejandro

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

*Python3 is nearly ready to merge, 4 oe-selftest issues remain and some 
toaster issues. There are likely others but the tests aren't showing them and 
I'm not getting bug reports so the code will merge once the known issues are 
addressed.

*gcc6 is about ready to merge, just one issue, linux-yocto-4.1 on 
beaglebone to address

*Patches are being held up as some large series (python3, gcc6) are 
needing testing and we're trying to get these done before moving to other 
patches. We're aware there is a backlog building again and will work through 
that as time and autobuilder resources allow.

*RP is out of contact Fri-Mon due to vacation/national holidays so this 
may delay some final merges, mut is continuing development. RP typically does a 
lot of testing over weekends to make the most of the autobuilder but this won't 
happen and hence there will be a slow down.

*YP 1.8.2 passed QA and is due for release shortly.

*YP 2.0.2 is in QA and will be out next week.


Key YP 2.2 Dates:

*YP 2.2 M1 cut off would be: 6/13/16

*YP 2.2 M1 release would be: 6/24/16

*YP 2.2 M2 cut off would be: 7/18/16

*YP 2.2 M2 release would be: 7/29/16

*YP 2.2 M3 cut off would be: 8/29/16

*YP 2.2 M3 release would be: 9/9/16

*YP 2.2 M4 cut off would be: 10/3/16

*YP 2.2 M4 release would be: 10/28/16


Tracking Metrics:

WDD 2574 (last week 2626)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features

[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

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.jol...@intel.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Status WW22

2016-05-27 Thread akuster



On 05/27/2016 08:14 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.2 M1
> 
> Next Deadline: YP 2.2 cut off: June 13, 2016
> 
> 
> SWAT team rotation: Tracy -> Alejandro
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> 
> Key Status/Updates:
> 
> *Python3 is nearly ready to merge, 4 oe-selftest issues remain and 
> some toaster issues. There are likely others but the tests aren't showing 
> them and I'm not getting bug reports so the code will merge once the known 
> issues are addressed.
> 
> *gcc6 is about ready to merge, just one issue, linux-yocto-4.1 on 
> beaglebone to address
> 
> *Patches are being held up as some large series (python3, gcc6) are 
> needing testing and we're trying to get these done before moving to other 
> patches. We're aware there is a backlog building again and will work through 
> that as time and autobuilder resources allow.
> 
> *RP is out of contact Fri-Mon due to vacation/national holidays so 
> this may delay some final merges, mut is continuing development. RP typically 
> does a lot of testing over weekends to make the most of the autobuilder but 
> this won't happen and hence there will be a slow down.
> 

If the autobuilder is going to idle this weekend, can we build
krogoth-next from

git://git.yoctoproject.org/poky-contrib akuster/krogoth-next

- armin


> *YP 1.8.2 passed QA and is due for release shortly.
> 
> *YP 2.0.2 is in QA and will be out next week.
> 
> 
> Key YP 2.2 Dates:
> 
> *YP 2.2 M1 cut off would be: 6/13/16
> 
> *YP 2.2 M1 release would be: 6/24/16
> 
> *YP 2.2 M2 cut off would be: 7/18/16
> 
> *YP 2.2 M2 release would be: 7/29/16
> 
> *YP 2.2 M3 cut off would be: 8/29/16
> 
> *YP 2.2 M3 release would be: 9/9/16
> 
> *YP 2.2 M4 cut off would be: 10/3/16
> 
> *YP 2.2 M4 release would be: 10/28/16
> 
> 
> Tracking Metrics:
> 
> WDD 2574 (last week 2626)
> 
> (https://wiki.yoctoproject.org/charts/combo.html)
> 
> 
> Key Status Links for YP:
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features
> 
> [If anyone has suggestions for other information you'd like to see on this 
> weekly status update, let us know!]
> 
> 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.jol...@intel.com
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [opkg-utils PATCH 1/2] migrate to python 3

2016-05-27 Thread Alejandro del Castillo

General fixes
* Add __future__ imports
* Use print function instead of print statement
* Use new style classes
* Iterate over list, instead of over object.keys()
* Use six.iteritems  instead of iteritems()

opkg.py:
* Add conditional to decode string if needed in Package:read_control

arfile.py
* Add seekable method to FileSection class (needed by tarfile)

Signed-off-by: Alejandro del Castillo 
---
 arfile.py| 10 --
 makePackage  |  2 ++
 opkg-compare-indexes |  2 ++
 opkg-graph-deps  | 39 +--
 opkg-list-fields |  2 ++
 opkg-make-index  |  2 ++
 opkg-show-deps   |  2 ++
 opkg-unbuild |  2 ++
 opkg-update-index|  1 +
 opkg.py  | 17 ++---
 10 files changed, 52 insertions(+), 27 deletions(-)

diff --git a/arfile.py b/arfile.py
index 88ace46..4bab526 100644
--- a/arfile.py
+++ b/arfile.py
@@ -5,12 +5,15 @@ Copyright (c) 2006-7 Paul Sokolovsky
 This file is released under the terms 
 of GNU General Public License v2 or later.
 """
+from __future__ import absolute_import
+from __future__ import print_function
+from builtins import object
 import sys
 import os
 import tarfile 
 
 
-class FileSection:
+class FileSection(object):
 "A class which allows to treat portion of file as separate file object."
 
 def __init__(self, f, offset, size):
@@ -30,6 +33,9 @@ class FileSection:
 else:
 assert False
 
+def seekable(self):
+return True 
+
 def tell(self):
 #print("tell()")
 return self.f.tell() - self.offset
@@ -38,7 +44,7 @@ class FileSection:
 #print("read(%d)" % size)
 return self.f.read(size)
 
-class ArFile:
+class ArFile(object):
 
 def __init__(self, f, fn):
 self.f = f
diff --git a/makePackage b/makePackage
index ec76338..4bdfc56 100755
--- a/makePackage
+++ b/makePackage
@@ -5,6 +5,8 @@
 #   Insert the filename, size, and md5 lines before the description.
 # Call it like this:
 #  find . -name \*.opk | xargs -n 1 makePackage > Packages
+from __future__ import absolute_import
+from __future__ import print_function
 
 import sys
 import opkg
diff --git a/opkg-compare-indexes b/opkg-compare-indexes
index 7bb3c69..b60d20a 100755
--- a/opkg-compare-indexes
+++ b/opkg-compare-indexes
@@ -1,4 +1,6 @@
 #!/usr/bin/env python
+from __future__ import absolute_import
+from __future__ import print_function
 
 import sys, os
 from glob import glob
diff --git a/opkg-graph-deps b/opkg-graph-deps
index d7f4fd2..6653fd5 100755
--- a/opkg-graph-deps
+++ b/opkg-graph-deps
@@ -1,18 +1,21 @@
 #!/usr/bin/env python
+from __future__ import absolute_import
+from __future__ import print_function
 
 import sys
 import os
 import getopt
 import pydot
 import opkg
+import six
 
 def usage(more=False):
-print >>sys.stderr, ( 'Usage: opkg-graph-deps '
+print(( 'Usage: opkg-graph-deps '
 '[-h] [-d] [-o feed.dot] '
 '[-u ] '
-'' )
+'' ), file=sys.stderr)
 if more:
-print >>sys.stderr, '\n'.join( [
+print('\n'.join( [
 '',
 'Generates a dot formatted dependency graph of an IPK feed.',
 '',
@@ -56,7 +59,7 @@ def usage(more=False):
 '  the alias != (to).',
 ' ipkBrokenDep: Set to "1" if (to) is missing from the feed.',
 '',
-] )
+] ), file=sys.stderr)
 exit(1)
 
 # optional args
@@ -76,19 +79,19 @@ for (optkey, optval) in opts:
 feed_url = optval
 
 if not index_files:
-print >>sys.stderr, 'Must specify a path to at least one Packages file'
+print('Must specify a path to at least one Packages file', file=sys.stderr)
 usage()
 
 def fatal_error(msg):
-print >>sys.stderr, ('ERROR: ' + str(msg))
+print(('ERROR: ' + str(msg)), file=sys.stderr)
 exit(1)
 
 def warn(msg):
-print >>sys.stderr, str(msg)
+print(str(msg), file=sys.stderr)
 
 def debug(msg):
 if enable_debug:
-print >>sys.stderr, ('DEBUG: ' + str(msg))
+print(('DEBUG: ' + str(msg)), file=sys.stderr)
 
 def split_dep_list(lst):
 '''
@@ -190,7 +193,7 @@ for indexFilePath in index_files:
 packages.read_packages_file(indexFilePath)
 
 # add each package
-for pkgKey in packages.keys():
+for pkgKey in list(packages.keys()):
 pkg = packages[pkgKey]
 
 # sanity check: verify important attributes are defined for
@@ -228,7 +231,7 @@ for indexFilePath in index_files:
 # provides the alias.
 # These packages are not added to the graph because their implementations
 # are already there.
-for pkgKey, pkg in real_pkg_map.iteritems():
+for pkgKey, pkg in six.iteritems(real_pkg_map):
 for alias in split_dep_list(pkg.provides):
 if alias not in active_pkg_map:
 # add it
@@ -260,7 +263,7 @@ for pkgKey, pkg in real_pkg_map.iteritems():
 virt_pkg_map[alias].append(pkg)
 
 # Print alternatives for virtual packages
-for pkgKey, pkgList in virt_pkg_map.iteritems():
+for pkgKey, pkgList in six.iter

[yocto] [opkg-utils PATCH 2/2] opkg.py/write_packages_file: call str instead of repr

2016-05-27 Thread Alejandro del Castillo

Commit b9eec00a67f13ad9f9526caf591578b40d73a391 correctly renamed
__repr__to __str__. A call site in write_packages_file was missed.

Signed-off-by: Alejandro del Castillo 
---
 opkg.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/opkg.py b/opkg.py
index fe6b9e0..2acc469 100644
--- a/opkg.py
+++ b/opkg.py
@@ -533,7 +533,7 @@ class Packages(object):
 names = list(self.packages.keys())
 names.sort()
 for name in names:
-f.write(self.packages[name].__repr__())
+f.write(self.packages[name].__str__())
 return
 
 def keys(self):
-- 
1.9.1

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

[yocto] [opkg-utils PATCH 0/2] migrate to python 3

2016-05-27 Thread Alejandro del Castillo

First patch migrates all opkg-utils scrips to python 3. opkg-graph-deps
doesn't work on python 3 since it depends on pydot, which hasn't migrated
to python 3. Second patch fixes opkg-update-index, which was broken.

Alejandro del Castillo (2):
  migrate to python 3
  opkg.py/write_packages_file: call __str__ instead of __repr__

 arfile.py| 10 --
 makePackage  |  2 ++
 opkg-compare-indexes |  2 ++
 opkg-graph-deps  | 39 +--
 opkg-list-fields |  2 ++
 opkg-make-index  |  2 ++
 opkg-show-deps   |  2 ++
 opkg-unbuild |  2 ++
 opkg-update-index|  1 +
 opkg.py  | 19 +++
 10 files changed, 53 insertions(+), 28 deletions(-)

-- 
1.9.1

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

Re: [yocto] On target gdb support for multiple architectures?

2016-05-27 Thread Stroz, Glenn

In this case there is not. It appears as if the aarch64 binary gets priority.

root@qcom-bsp:/# find -name gdb
find: ./proc/7639: No such file or directory
./usr/share/gdb
./usr/bin/gdb
find: ./sys/kernel/slab/L2TP/IPv6: No such file or directory
find: ./sys/kernel/slab/L2TP/IP: No such file or directory
root@qcom-bsp:/#

/usr/share/gdb is a folder


The image file has the following:

IMAGE_INSTALL += "gdb"
IMAGE_INSTALL += "lib32-gdb"

Ideally we would like one binary that is capable of debugging both 
architectures, but two binaries would be a short term workaround.

-Glenn

From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Friday, May 27, 2016 12:20 AM
To: Stroz, Glenn 
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] On target gdb support for multiple architectures?


There should be two gdb executables on your target.
On May 26, 2016 3:34 PM, "Stroz, Glenn" 
mailto:gst...@qti.qualcomm.com>> wrote:
Hello,

We’re trying to setup our target for onboard debugging. We have multiple 
architectures being built with multilib. An armv7 variant which is 32 bit and 
an armv8 variant which is 64 bit. We would like the gdb installed in the image 
to support both architectures. Right now, even when adding both gdb and 
lib32-gdb to the image we see it only supports aarch64.

#
# Multilib configuration
#
# This sets any packages preprended with lib32- to be built with
# the armv7a tuning (32 bit) instead of 64 bit aarch.
#
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "armv7a-neon"

When adding lib32-gdb and gdb to image:
(gdb) set architecture
Requires an argument. Valid arguments are aarch64, aarch64:ilp32, auto.

When adding only lib32-gdb to image:
(gdb) set architecture
Requires an argument. Valid arguments are arm, armv2, armv2a, armv3, armv3m, 
armv4, armv4t, armv5, armv5t, armv5te, xscale, ep9312, iwmmxt, iwmmxt2, auto.

Is there any method of getting the build system to combine the two lists of 
architectures into one binary that supports them all?

Thanks,
Glenn

--
___
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] [ANNOUNCEMENT] Yocto Project 1.8.2 (Fido 13.0.2) Released

2016-05-27 Thread Tracy Graydon

Hello,

The latest release of the Yocto Project 1.8.2 (fido-13.0.2) is now available
for download at:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.8.2/poky-fido-13.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.8.2/poky-fido-13.0.2.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.8.2/RELEASENOTES

Full pass test report is available at:

https://wiki.yoctoproject.org/wiki/WW21_-_2016-05-13_-_Full_Pass_1.8.2

Thanks go out to everyone for all their hard work during this release!

Sincerely,

Tracy Graydon
Yocto Project
Build and Release

---
yocto-1.8.2 Errata
-

Release Name: eclipse-poky-kepler-fido-13.0.2
Branch: kepler/fido
Tag: kepler/fido-13.0.2
Hash: cf60ac293629fc8ecd6c4eb3709a6f334b499d0c
md5: dbc764d5c8687d29480b165997ad516e
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.8.2/eclipse-poky-kepler-fido-13.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.8.2/eclipse-poky-kepler-fido-13.0.2.tar.bz2

Release Name: eclipse-poky-luna-fido-13.0.2
Branch: luna/fido
Tag: luna/fido-13.0.2
Hash: 45aa5c77523bdf051d548fff4305382942db2ebb
md5: 619373f7c5b57d6e8e1f059a8fc2beb0
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.8.2/eclipse-poky-luna-fido-13.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.8.2/eclipse-poky-luna-fido-13.0.2.tar.bz2

Release Name: meta-qt3-fido-13.0.2
Branch: fido
Tag: fido-13.0.2
Hash: 83bcdf8ee8c194707daa34d852f619844d30f287
md5: 871c02a81702de34be4571b3f9601272
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.8.2/meta-qt3-fido-13.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.8.2/meta-qt3-fido-13.0.2.tar.bz2

Release Name: poky-fido-13.0.2
Branch: fido
Tag: fido-13.0.2
Hash: c9f0a99050ec0050f0dbcd55d0cd2ab18848113f
md5: 9eaa656682e0e76b2d051ff50d272ac2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.8.2/poky-fido-13.0.2.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.8.2/poky-fido-13.0.2.tar.bz2



 Known Issues

n/a


Security Fixes

openssl: 1.0.2d -> 1.0.2h (mainly for CVEs)
bind: CVE-2016-1285 CVE-2016-1286
dhcp: CVE-2015-8605
openssl: Security fix CVE-2016-0800
wpa-supplicant: Fix CVE-2015-8041
git: Security fixes CVE-2015-7545
nettle: Security fix CVE-2015-8804
nettle: Security fix CVE-2015-8803 and CVE-2015-8805
bind: Security fix CVE-2015-8461
rpcbind: Security Advisory - rpcbind - CVE-2015-7236
curl: Secuirty fix CVE-2016-0755
curl: Security fix CVE-2016-0754
libgcrypt: Security fix CVE-2015-7511
libpng: Security fix CVE-2015-8472
libpng: Security fix CVE-2015-8126
gdk-pixbuf: Security fix CVE-2015-7674
librsvg: Security fix CVE-2015-7558
tiff: Security fix CVE-2015-8784
tiff: Security fix CVE-2015-8781
foomatic-filters: Security fixes CVE-2015-8327
foomatic-filters: Security fix CVE-2015-8560
qemu: Security fix CVE-2016-2198
libbsd: Security fix CVE-2016-2090
glibc: Security fix CVE-2015-7547
dpkg: Security fix CVE-2015-0860
bind: Security fix CVE-2015-8704
libxml2: Security fix CVE-2015-8710
libxml2: Security fix CVE-2015-8241
qemu: Security fix CVE-2015-7295
qemu: Security fix CVE-2016-1568
qemu: Security fix CVE-2015-8345
qemu: Security fix CVE-2015-7512
qemu: Security fix CVE-2015-7504
qemu: Security fix CVE-2015-8504
subversion: fix CVE-2015-3187
subversion: fix CVE-2015-3184
openssl: Security fix CVE-2016-0701
openssl: Security fix CVE-2015-3197
glibc: CVE-2015-8776
glibc: CVE-2015-9761
glibc: CVE-2015-8779
glibc: CVE-2015-8777
openssh: CVE-2016-077x
libxml2: security fix CVE-2015-5312
libxml2: security fix CVE-2015-8242
libxml2: security fix CVE-2015-7500
libxml2: security fix CVE-2015-7499
libxml2: security fix CVE-2015-7497
libxml2: security fix CVE-2015-7498
libxml2: security fix CVE-2015-8035
libxml2: security fix CVE-2015-7942
libxml2: security fix CVE-2015-8317
libxml2: security fix CVE-2015-7941
openssl: fix for CVE-2015-3195
openssl: fix for CVE-2015-3194
openssl: fix for CVE-2015-3193
grub2: Fix CVE-2015-8370
bind: CVE-2015-8000
libxml2: fix CVE-2015-7942 and CVE-2015-8035
readline: actually apply readline63-003 (aka CVE-2014-2524)
openssh: Backport CVE-2015-5600 fix
unzip: CVE-2015-7696, CVE-2015-7697
libxslt: CVE-2015-7995



Fixes

build-appliance-image: Update to fido head revision
openssl: prevent ABI break from earlier fido releases
conf/local.conf.sample: comment out ASSUME_PROVIDED=libsdl-native
build-appliance-image: Update to fido head revision
bitbake: tests/fetch: ensure fetch tests preserve current dir
bitbake: bb/tests/fetch: Update cups url
gtk+_2.24.25: backport a fix for building with newer host perl
tzdata: update to 2016d
tzcode: update to 2016d
tzcode: update to 2016c
tzdata: update to 2016c
tzcode: update to 2016b
tzdata: update to 2016b
busybox_git: Fix SRCREV

Re: [yocto] On target gdb support for multiple architectures?

2016-05-27 Thread Khem Raj

On Sat, May 28, 2016 at 1:33 AM, Stroz, Glenn  wrote:
> In this case there is not. It appears as if the aarch64 binary gets
> priority.
>
>
>
> root@qcom-bsp:/# find -name gdb
>
> find: ./proc/7639: No such file or directory
>
> ./usr/share/gdb
>
> ./usr/bin/gdb
>
> find: ./sys/kernel/slab/L2TP/IPv6: No such file or directory
>
> find: ./sys/kernel/slab/L2TP/IP: No such file or directory
>
> root@qcom-bsp:/#
>
>
>
> /usr/share/gdb is a folder
>
>
>
>
>
> The image file has the following:
>
>
>
> IMAGE_INSTALL += "gdb"
>
> IMAGE_INSTALL += "lib32-gdb"
>
>
>
> Ideally we would like one binary that is capable of debugging both

Keep in mind that mutlilib was a adhoc solution to keep running 32bit software
on 64bit arches. So minimally all you get is a 32bit runtime which is capable of
doing the same. Since these programs are debugged well and are supposed to run
out of box due to there legacy, to have multllib tools has less value.

having said that, you can add --enable-targets= for gdb and
binutils as well
to get some capabilities to debug the system.

> architectures, but two binaries would be a short term workaround.
>
>
>
> -Glenn
>
>
>
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Friday, May 27, 2016 12:20 AM
> To: Stroz, Glenn 
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] On target gdb support for multiple architectures?
>
>
>
> There should be two gdb executables on your target.
>
> On May 26, 2016 3:34 PM, "Stroz, Glenn"  wrote:
>
> Hello,
>
>
>
> We’re trying to setup our target for onboard debugging. We have multiple
> architectures being built with multilib. An armv7 variant which is 32 bit
> and an armv8 variant which is 64 bit. We would like the gdb installed in the
> image to support both architectures. Right now, even when adding both gdb
> and lib32-gdb to the image we see it only supports aarch64.
>
>
>
> #
>
> # Multilib configuration
>
> #
>
> # This sets any packages preprended with lib32- to be built with
>
> # the armv7a tuning (32 bit) instead of 64 bit aarch.
>
> #
>
> require conf/multilib.conf
>
> MULTILIBS = "multilib:lib32"
>
> DEFAULTTUNE_virtclass-multilib-lib32 = "armv7a-neon"
>
>
>
> When adding lib32-gdb and gdb to image:
>
> (gdb) set architecture
>
> Requires an argument. Valid arguments are aarch64, aarch64:ilp32, auto.
>
>
>
> When adding only lib32-gdb to image:
>
> (gdb) set architecture
>
> Requires an argument. Valid arguments are arm, armv2, armv2a, armv3, armv3m,
> armv4, armv4t, armv5, armv5t, armv5te, xscale, ep9312, iwmmxt, iwmmxt2,
> auto.
>
>
>
> Is there any method of getting the build system to combine the two lists of
> architectures into one binary that supports them all?
>
>
>
> Thanks,
>
> Glenn
>
>
> --
> ___
> 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] On target gdb support for multiple architectures?

[yocto] Systemd-udevd cache

Re: [yocto] [PATCH][matchbox-wm] wm: Do not set MB theme based on Net/ThemeName

[yocto] Yocto Project Status WW22

Re: [yocto] Yocto Project Status WW22

[yocto] [opkg-utils PATCH 1/2] migrate to python 3

[yocto] [opkg-utils PATCH 2/2] opkg.py/write_packages_file: call str instead of repr

[yocto] [opkg-utils PATCH 0/2] migrate to python 3

Re: [yocto] On target gdb support for multiple architectures?

[yocto] [ANNOUNCEMENT] Yocto Project 1.8.2 (Fido 13.0.2) Released

Re: [yocto] On target gdb support for multiple architectures?

11 matches

Site Navigation

Mail list logo

Footer information