[yocto] [RFT] binutils 2.27

2016-08-07 Thread Khem Raj
Hi All

I have put together upgrade for binutils 2.27 here ( kraj/master branch )

https://github.com/kraj/openembedded-core/commit/b98f5761d2285ffd773ec6ecb901b799302ebd6b

I have started bunch of test builds. but I would appreciate any help in testing 
it out in your
environments and report any issues you see.

Thanks

-Khem



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-virtualization][PATCH] Fix build error for arm

2016-08-07 Thread kai.kang
From: Kai Kang 

When build for qemuarm, it fails to do compile_ptest_base.

Kai Kang (1):
  libvirt: fix build error for arm

 .../0001-nsslinktest-also-build-virAtomic.h.patch  | 40 ++
 recipes-extended/libvirt/libvirt_1.3.5.bb  |  1 +
 2 files changed, 41 insertions(+)
 create mode 100644 
recipes-extended/libvirt/libvirt/0001-nsslinktest-also-build-virAtomic.h.patch

-- 
2.9.2.368.g08bb350

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


[yocto] [PATCH] libvirt: fix build error for arm

2016-08-07 Thread kai.kang
From: Kai Kang 

When build for architecture that don't use gcc atomic ops but pthread,
it fails to build for arm:

| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virClassNew':
| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:153:
 undefined reference to `virAtomicLock'
| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virObjectNew':
| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:205:
 undefined reference to `virAtomicLock'
| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virObjectUnref':
| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:277:
 undefined reference to `virAtomicLock'
| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virObjectRef':
| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:298:
 undefined reference to `virAtomicLock'
| collect2: error: ld returned 1 exit status

It is similar with:

http://libvirt.org/git/?p=libvirt.git;a=commit;h=12dc729

Signed-off-by: Kai Kang 
---
 .../0001-nsslinktest-also-build-virAtomic.h.patch  | 40 ++
 recipes-extended/libvirt/libvirt_1.3.5.bb  |  1 +
 2 files changed, 41 insertions(+)
 create mode 100644 
recipes-extended/libvirt/libvirt/0001-nsslinktest-also-build-virAtomic.h.patch

diff --git 
a/recipes-extended/libvirt/libvirt/0001-nsslinktest-also-build-virAtomic.h.patch
 
b/recipes-extended/libvirt/libvirt/0001-nsslinktest-also-build-virAtomic.h.patch
new file mode 100644
index 000..6ab1c4e
--- /dev/null
+++ 
b/recipes-extended/libvirt/libvirt/0001-nsslinktest-also-build-virAtomic.h.patch
@@ -0,0 +1,40 @@
+Upstream-Status: Submitted 
[http://www.redhat.com/archives/libvir-list/2016-August/msg00389.html]
+
+When build for architecture that don't use gcc atomic ops but pthread,
+it fails to build for arm:
+
+| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virClassNew':
+| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:153:
 undefined reference to `virAtomicLock'
+| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virObjectNew':
+| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:205:
 undefined reference to `virAtomicLock'
+| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virObjectUnref':
+| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:277:
 undefined reference to `virAtomicLock'
+| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In 
function `virObjectRef':
+| 
/buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:298:
 undefined reference to `virAtomicLock'
+| collect2: error: ld returned 1 exit status
+
+It is similar with:
+
+http://libvirt.org/git/?p=libvirt.git;a=commit;h=12dc729
+
+Signed-off-by: Kai Kang 
+---
+ src/Makefile.am | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 12b66c2..6e55972 100644
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -2989,6 +2989,8 @@ noinst_LTLIBRARIES += libvirt-nss.la
+ libvirt_nss_la_SOURCES =  \
+   util/viralloc.c \
+   util/viralloc.h \
++  util/viratomic.c\
++  util/viratomic.h\
+   util/virbitmap.c\
+   util/virbitmap.h\
+   util/virbuffer.c\
+-- 
+2.9.0
+
diff --git a/recipes-extended/libvirt/libvirt_1.3.5.bb 
b/recipes-extended/libvirt/libvirt_1.3.5.bb
index f4a8f38..7ff2c5f 100644
--- a/recipes-extended/libvirt/libvirt_1.3.5.bb
+++ b/recipes-extended/libvirt/libvirt_1.3.5.bb
@@ -33,6 +33,7 @@ SRC_URI = 
"http://libvirt.org/sources/libvirt-${PV}.tar.gz;name=libvirt \
file://0001-to-fix-build-error.patch \
file://Revert-build-add-prefix-to-SYSTEMD_UNIT_DIR.patch \
file://install-missing-file.patch \
+   file://0001-nsslinktest-also-build-virAtomic.h.patch \
   "
 
 SRC_URI[libvirt.md5sum] = "f9dc1e63d559eca50ae0ee798a4c6c6d"
-- 
2.9.2.368.g08bb350


[yocto] [Recipe reporting system] Upgradable recipe name list

2016-08-07 Thread recipe-report
This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   VersionUpstream version  Maintainer   
NoUpgradeReason
  -    ---  
--
perl  5.22.1 5.24.1Alejandro Hernandez
python3-setuptools22.0.5 25.1.6Alejandro Hernandez
texinfo   6.06.1   Alejandro Hernandez
swig  3.0.8  3.0.10Alejandro Hernandez
python-git2.0.7  2.0.8 Alejandro Hernandez
ruby  2.2.5  2.3.1 Alejandro Hernandez
python-setuptools 22.0.5 25.1.6Alejandro Hernandez
python3   3.5.1  3.5.2 Alejandro Hernandez
python2.7.11 2.7.12Alejandro Hernandez
nfs-utils 1.3.3  1.3.4 Alejandro Hernandez
python-native 2.7.11 2.7.12Alejandro Hernandez
python3-git   2.0.7  2.0.8 Alejandro Hernandez
python3-native3.5.1  3.5.2 Alejandro Hernandez
perl-native   5.22.1 5.24.1Alejandro Hernandez
lighttpd  1.4.39 1.4.41Alexander Kanavin
liberation-fonts  1.04   2.00.1Alexander Kanavin
2.x depends on fontforge pa...
gobject-introspec...  1.48.0 1.49.1Alexander Kanavin
procps3.3.11 3.3.12Alexander Kanavin
btrfs-tools   4.6.1  4.7   Alexander Kanavin
mpg1231.23.5 1.23.6Alexander Kanavin
libidn1.32   1.33  Alexander Kanavin
libwebp   0.5.0  0.5.1 Alexander Kanavin
iso-codes 3.68   3.69  Alexander Kanavin
gnutls3.5.1  3.5.2 Alexander Kanavin
nss   3.24   3.25  Alexander Kanavin
mkelfimage4.0+gitX   4.4+gitAUTOINC+58...  Alexander Kanavin
mkelfimage has been removed...
dpkg  1.18.7 1.18.10   Aníbal Limón
pinentry  0.9.2  0.9.7 Armin Kuster
linux-libc-headers4.44.7   Bruce Ashfield
guilt-native  0.35+gitX  0.36+gitAUTOINC+2...  Bruce Ashfield
kmod  22+gitX23+gitAUTOINC+65a...  Chen Qi
curl  7.49.1 7.50.1Chen Qi
kmod-native   22+gitX23+gitAUTOINC+65a...  Chen Qi
systemd   230+gitX   231+gitAUTOINC+38...  Chen Qi
u-bootv2016.03+gitX  v2016.07+gitAUTOI...  Denys Dmytriyenko
u-boot-fw-utils   v2016.03+gitX  v2016.07+gitAUTOI...  Denys Dmytriyenko
u-boot-mkimagev2016.03+gitX  v2016.07+gitAUTOI...  Denys Dmytriyenko
man-pages 4.06   4.07  Hongxu Jia
createrepo0.4.11 0.10.4Hongxu Jia   
Versions after 0.9.* use YU...
libgcrypt 1.7.0  1.7.2 Hongxu Jia
ncurses   6.0+20160319   6.0+20160625  Hongxu Jia
gnupg 2.1.12 2.1.14Hongxu Jia
xf86-input-synaptics  1.8.3  1.8.99.1  Jussi Kukkonen
libinput  1.3.0  1.4.1 Jussi Kukkonen
gtk-icon-utils-na...  3.20.6 3.20.8Jussi Kukkonen
openssh   7.2p2  7.3p1 Jussi Kukkonen
libdrm2.4.68 2.4.70Jussi Kukkonen
gtk+3 3.20.6 3.20.8Jussi Kukkonen
sgmlspl-native1.1+gitX   1.03+gitAUTOINC+f...  Jussi Kukkonen
fontconfig2.12.0 2.12.1Jussi Kukkonen
json-glib 1.2.0  1.2.2 Jussi Kukkonen
vte   0.44.1 0.44.2Jussi Kukkonen
prelink   1.0+gitX   20151030.+gitAUTO...  Mark Hatle
rpm   5.4.16 5.4.17Mark Hatle
db6.0.30 6.2.23Mark Hatle   
latest db does not work wit...
libpfm4   4.6.0  4.7.0 Matth

Re: [yocto] [OE-core] [RFT] binutils 2.27

2016-08-07 Thread Richard Purdie
On Sun, 2016-08-07 at 01:39 -0700, Khem Raj wrote:
> I have put together upgrade for binutils 2.27 here ( kraj/master
> branch )
> 
> https://github.com/kraj/openembedded-core/commit/b98f5761d2285ffd773e
> c6ecb901b799302ebd6b
> 
> I have started bunch of test builds. but I would appreciate any help
> in testing it out in your
> environments and report any issues you see.

I ran this through the autobuilder:

bitbake world shows issues in libunwind (from gold?):

https://autobuilder.yoctoproject.org/main/builders/nightly-world/builds
/889/steps/BuildImages/logs/stdio

bitbake world with no x11 also shows it:

https://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/build
s/231/steps/BuildImages/logs/stdio

Other than that, things don't seem too bad though.

Cheers,

Richard


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


[yocto] Antwort: Re: Antwort: Re: How to set the sysroot toolchain to hard float

2016-08-07 Thread S . Jaritz
Hej ho

Thank you. I already know the files. My question was targeting the way how 
to set the tune option manually.

Maybee something is missed up by the layers. My bblayers.conf looks like:
#
# POKY_BBLAYERS_CONF_VERSION is increased each time 
build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"

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

BBLAYERS ?= " \
myTC/poky/meta \
myTC/poky/meta-poky \
myTC/poky/meta-yocto-bsp \
myTC/poky/meta-atmel \
myTC/poky/meta-skeleton \
myTC/poky/meta-openembedded/meta-oe \
myTC/poky/meta-openembedded/meta-networking \
myTC/poky/meta-openembedded/meta-python \
myTC/poky/meta-mylayer \
"
#

The priorities are set that way:

BBFILE_PRIORITY_atmel = "10"
BBFILE_PRIORITY_mylayer = "20"

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"robert.berger@gmane" 
An: yocto@yoctoproject.org
Kopie:  public-yocto-EtnWKYl6rD/WsZ/bQMPhNw 
, Khem Raj 

Datum:  06.08.2016 09:23
Betreff:Re: [yocto] Antwort: Re: How to set the sysroot toolchain 
to hard float
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,

On 2016-08-05 10:24, s.jar...@esa-grimma.de wrote:
>
> @TOOLCHAIN_OPTIONS: Where these are set in custom layers(like 
meta-atmel)?
>

If you ask me I would say here [1]:

DEFAULTTUNE = "cortexa5thf"

Here [2] are the available HF options:

# HF Tunes
AVAILTUNES += "cortexa5hf cortexa5thf cortexa5hf-neon cortexa5thf-neon"

[1] 
https://github.com/linux4sam/meta-atmel/blob/master/conf/machine/include/sama5d3.inc

[2] 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/machine/include/tune-cortexa5.inc


Regards,

Robert


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

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