[OE-core] [PATCH V2 0/1] systemd: add option for valgrind header checking

The following changes since commit 33b7885ecdc8774e34ac3534ec49fed6ffdb3916: oprofile: 0.9.9 -> 1.0.0 (2014-11-09 10:19:58 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib ChenQi/systemd-valgrindheader http://cgit.openembedded.org/cgit.c

[OE-core] [PATCH V2 1/1] systemd: add option for valgrind header checking

Add option so that valgrind header checking is controlled. Otherwise, we would get the following error. src/libsystemd/sd-bus/bus-control.c: fatal error: valgrind/mencheck.h: No such file or directory The above error could be reproduced by the following command. bitbake valgrind && bitbake s

Re: [OE-core] [PATCH 1/1] systemd: add option for valgrind header checking

On 11/12/2014 11:55 PM, Burton, Ross wrote: On 12 November 2014 10:45, Chen Qi > wrote: +-AC_CHECK_HEADERS_ONCE([valgrind/memcheck.h valgrind/valgrind.h]) ++AC_ARG_ENABLE(valgrindheader, AS_HELP_STRING([--disable-valgrindheader], [disable valgrind he

Re: [OE-core] [PATCH 1/3] avahi.inc: rename package to use avahi to instead of avahi-daemon

* Hongxu Jia [141113 02:44]: > On 11/13/2014 09:28 AM, Hongxu Jia wrote: > > On 11/12/2014 06:27 PM, Koen Kooi wrote: > >>> Op 11 nov. 2014, om 11:52 heeft Hongxu Jia > >>> het volgende geschreven: > >>> The package avahi does not exist, as SUMMARY said, we should > >>> use avahi-daemon to ins

Re: [OE-core] [PATCH] automake: set test-driver path relative to top_builddir

Hi Ross, This patch was required by two changes done in Yocto but I think is a very good point to discuss first with automake maintainers. So we can avoid carrying this path. Thanks, Adrian From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Wednesday, November 12, 2014 7:5

[OE-core] [PATCH 1/2] tcl: Upgrade to 8.6.3

Signed-off-by: Chong Lu --- meta/recipes-devtools/tcltk/{tcl_8.6.2.bb => tcl_8.6.3.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-devtools/tcltk/{tcl_8.6.2.bb => tcl_8.6.3.bb} (95%) diff --git a/meta/recipes-devtools/tcltk/tcl_8.6.2.bb b/meta/recipes-devtools

[OE-core] [PATCH 0/2] Upgrade two packages

The following changes since commit edaeb8940813b620090a0797ad3b6a076897512d: bitbake: cooker.py: fix loginfo op being set to an invalid value (2014-11-12 17:04:50 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib chonglu/tcl http://git.pokylinux.org/cgit.

[OE-core] [PATCH 2/2] byacc: Upgrade to 20141006

Signed-off-by: Chong Lu --- meta/recipes-extended/byacc/{byacc_20140715.bb => byacc_20141006.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/byacc/{byacc_20140715.bb => byacc_20141006.bb} (74%) diff --git a/meta/recipes-extended/byacc/byacc_20140715.b

Re: [OE-core] [PATCH 1/3] avahi.inc: rename package to use avahi to instead of avahi-daemon

On 11/13/2014 04:27 PM, Anders Darander wrote: Koen means that you should use IMAGE_INSTALL_append += "avahi-daemon" and not avahi... (I.e. package name, not recipe name). If you still insist on creating a package named avahi, you might as well create avahi as an empty package, RDEPEND'ing on al

[OE-core] [PATCH] gcc-4.9: fix the compile failure of 'defaults.h' not found

While compiling gcc-crosssdk-initial-x86_64 on some host, there is occasionally failure that test the existance of default.h doesn't work. ... | tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/calls.c:1240: error: 'STACK_CHECK_MAX_VAR_SIZE' was not declared in this scope ... The reason is tm_include_li

[OE-core] [PATCH 0/1] gcc-4.9: fix the compile failure of 'defaults.h' not found

The following changes since commit 3c741a8d33acbf4b3d5eecc04533bc76e2f37253: oprofile: 0.9.9 -> 1.0.0 (2014-11-09 10:21:24 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib hongxu/fix-gcc http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/fix-gcc

[OE-core] [PATCH 1/1] gcc-4.9: fix the compile failure of 'defaults.h' not found

While compiling gcc-crosssdk-initial-x86_64 on some host, there is occasionally failure that test the existance of default.h doesn't work. ... | tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/calls.c:1240: error: 'STACK_CHECK_MAX_VAR_SIZE' was not declared in this scope ... The reason is tm_include_li

Re: [OE-core] [RFC 07/14] qt-mobility: switch to virtual/bluez

On Wed, 2014-11-12 at 07:48 -0600, Peter A. Bigot wrote: > You raise some good questions. I'll come back to whether the name for > "whatever provides build-time support for bluetooth" should be spelled > "virtual/bluez" or something else. Naming is probably the least of the worries here. I will

Re: [OE-core] [RFC] Replace procps with procps-ng

On 11 November 2014 09:00, Koen Kooi wrote: > >> Op 10 nov. 2014, om 11:38 heeft Paul Barker het >> volgende geschreven: >> >> Hi all, >> >> I've tried upstreaming a patch against procps by sending it to the >> listed maintainer and the mailing list and I've had no reply from >> either. The last

Re: [OE-core] [PATCH 0/2] reporter-error sending report

On Wed, Nov 12, 2014 at 09:08:37PM -0200, João Henrique Ferreira de Freitas wrote: > When the Error Reporting Tool is enabled and the build fails, then the > report-error > prints an url that the user needs to get and use the send-error-report tool > which > will sends the reporter to a public

Re: [OE-core] [RFC 07/14] qt-mobility: switch to virtual/bluez

On 11/13/2014 04:06 AM, Richard Purdie wrote: On Wed, 2014-11-12 at 07:48 -0600, Peter A. Bigot wrote: You raise some good questions. I'll come back to whether the name for "whatever provides build-time support for bluetooth" should be spelled "virtual/bluez" or something else. Naming is proba

Re: [OE-core] [PATCH] nfs-utils: Upgrade to 1.3.1

On Wednesday 12 November 2014 11:16:38 Saul Wold wrote: > On 11/12/2014 10:50 AM, Alejandro Hernandez wrote: > > Removed: fix-a-Gcc-undefined-behavior.patch - Upstream > > > > Removed: 0001-statd-fixed-the-with-statdpath-flag.patch - Upstream > > > > Removed: fix-the-start-statd.patch - Different

Re: [OE-core] need help in qt environment setup

13.11.2014 09:20, Yi Qingliang пишет: > and then use '${OE_QMAKE_QMAKE}' but not 'qmake' directly. > > On Thu, Nov 13, 2014 at 2:18 PM, Yi Qingliang > mailto:niqingliang2...@gmail.com>> wrote: > > mkdir -p recipes-qt/meta > touch meta-ide-qte-support.bb > >

Re: [OE-core] [daisy][PATCH] file: add wrapper to nativesdk-file

Ping (hopefully to be included in daisy point release 1.6.2) - Regards, Javier Viguera On 20/10/14 12:13, Javier Viguera wrote: Backport commit 69a3ab3 to 'daisy' which uses a different version of file package. Author of the original patch: Hongxu Jia Signed-off-by: Javier Viguera ---

[OE-core] [PATCH] bind: use PACKAGE_BEFORE_PN instead of PACKAGES_prepend

Appending or prepending to PACKAGES breaks when the package is built natively, so use PACKAGE_BEFORE_PN instead. Signed-off-by: Ross Burton --- meta/recipes-connectivity/bind/bind_9.9.5.bb |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-connectivity/bind/bind_

[OE-core] [PATCH 0/1] toolchain-shar-template.sh: fix the text files in the top dir

The following changes since commit e7b731a1a358e0007dba1038ad504888bec5916e: docbook-xsl-stylesheets: fix do_configure typo (2014-11-12 15:36:14 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/sdk http://cgit.openembedded.org/cgit.cgi

[OE-core] [PATCH 1/1] toolchain-shar-template.sh: fix the text files in the top dir

It only fixed the text files in native_sysroot, but there might be some files in the top installed dir (whose var name is target_sdk_dir in the code) which are also needed to be fixed. It used "find $native_sysroot", now also "find $target_sdk_dir -maxdepth 1", and split the long line into small o

[OE-core] [PATCH] spdx.bbclass: improved error handling and code cleanup

The spdx task now writes a meaningful error message in case of error in communication with the FOSSology server. Also the coding style is now more consistent and some unneccessary calls/functions are removed. Signed-off-by: Tobias Olausson --- meta/classes/spdx.bbclass | 254

Re: [OE-core] [PATCH 00/24] V2: Add machine qemuarm64

CC:ing Steve M. from ARM who went through various arm naming issues for debian. > Op 7 nov. 2014, om 15:27 heeft Mark Hatle het > volgende geschreven: > > On 11/7/14, 3:18 AM, Koen Kooi wrote: >> >>> Op 7 nov. 2014, om 09:51 heeft Kai Kang het >>> volgende geschreven: >>> >>> V2: >>> * reba

[OE-core] [master][dizzy][PATCH] shadow-securetty: add ttyAM[0-3] serial ports

Old version of the ARM AMBA serial port driver creates those device nodes. Signed-off-by: Javier Viguera --- meta/recipes-extended/shadow/files/securetty | 4 1 file changed, 4 insertions(+) diff --git a/meta/recipes-extended/shadow/files/securetty b/meta/recipes-extended/shadow/files/sec

Re: [OE-core] [master][dizzy][PATCH] shadow-securetty: add ttyAM[0-3] serial ports

On Thu, Nov 13, 2014 at 1:48 PM, Javier Viguera wrote: > Old version of the ARM AMBA serial port driver creates those device nodes. > > Signed-off-by: Javier Viguera Acked-by: Otavio Salvador -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp:/

Re: [OE-core] [PATCH] Replace Python 3.3.x with Python 3.4.2

Hi Artur, On 12 November 2014 22:55, wrobell wrote: > Replace Python 3.3.x with Python 3.4.2 (bug #6857) > This patch has long lines so didn't survive SMTP, can you push it to a git repository somewhere? > Despite further work needed, I hope this patch can be merged, so further > work on Pyth

Re: [OE-core] [PATCH 1/2] midori: update to 0.5.8

Hi Andreas, On 7 November 2014 07:52, Andreas Müller wrote: > +SRC_URI = " > http://www.midori-browser.org/downloads/${BPN}_${PV}_all_.tar.bz2 \ > ERROR: Fetcher failure: Fetch command failed with exit code 8, output: http://www.midori-browser.org/downloads/midori_0.5.8_all_.tar.bz2: 2014-11-13

Re: [OE-core] [PATCH] Replace Python 3.3.x with Python 3.4.2

On Thu, Nov 13, 2014 at 5:24 PM, Burton, Ross wrote: > Hi Artur, > > On 12 November 2014 22:55, wrobell wrote: >> >> Replace Python 3.3.x with Python 3.4.2 (bug #6857) > > > This patch has long lines so didn't survive SMTP, can you push it to a git > repository somewhere? I have attached it to b

Re: [OE-core] [oe] Opkg files at /var/lib/opkg/lists

Hi Alejandro, Le Thu, 13 Nov 2014 14:10:12 -0600, Alejandro del Castillo a écrit : > I think you got it, the commit d950ef40a3eae4b54cc62828e66d84a62d78c447 > removed: > > rm -f ${IMAGE_ROOTFS}${OPKGLIBDIR}/opkg/lists/* > > step that I didn't see implemented on rootfs.py. I'll file a

Re: [OE-core] [PATCH] Replace Python 3.3.x with Python 3.4.2

On 13 November 2014 20:23, Artur Wroblewski wrote: > > Personally I'd prefer to see a working Python 3.4 integrated in one go > > instead of having a broken 3.4 integrated for an unknown about of time. > > Hopefully anyone else who is interested in 3.4 can step up and work on > the > > outstandin

Re: [OE-core] [PATCH v3] libsanitizer: Enable GCC sanitizers

On 4 November 2014 07:45, Burton, Ross wrote: > Hi Dan, > > On 16 September 2014 19:45, Dan McGregor wrote: >> >> No worries. There's a new version up now. I did some experiments with >> other machines. Turns out it doesn't >> work on aarch64. > > > Said I'd merge these once 1.7 out and sadly the

[OE-core] [PATCH 0/2] Upgrades

The following changes since commit dacc4ce59e48129a1a1e5316e10780f7358e29ef: nativesdk-cmake: Adjust toolchain paths dynamically (2014-10-24 21:59:46 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib hsalejandro/updates http://git.yoctoproject.org/cgit

[OE-core] [PATCH 2/2 v2] cronie: Upgrade to 1.4.12

Fixed license BSD, it should've been BSD-3 & BSD-2 Added license GPLv2+ according to upstream Patch fix-out-of-tree-build removed; already on upstream. Signed-off-by: Alejandro Hernandez --- .../cronie/cronie/fix-out-of-tree-build.patch | 31 -- .../cronie/{cronie_1.4.

[OE-core] [PATCH 1/2 v2] nfs-utils: Upgrade to 1.3.1

Removed: fix-a-Gcc-undefined-behavior.patch - Upstream Removed: 0001-statd-fixed-the-with-statdpath-flag.patch - Upstream Removed: fix-the-start-statd.patch - Different solution on upstream Removed: nfs-utils-1.0.6-uclibc.patch - Different solution on upstream Signed-off-by: Alejandro Hernandez

Re: [OE-core] [PATCH] Replace Python 3.3.x with Python 3.4.2

On Thu, Nov 13, 2014 at 10:52 PM, Burton, Ross wrote: > On 13 November 2014 20:23, Artur Wroblewski wrote: >> >> > Personally I'd prefer to see a working Python 3.4 integrated in one go >> > instead of having a broken 3.4 integrated for an unknown about of time. >> > Hopefully anyone else who is