Status Update
In summary its been a fairly quiet week, there are number of different holidays in different geos.
Pending Patches
===============
There has been a steady stream of 1.5 patches starting to appear. With Saul's help these have been tested on the autobuilder and then many have been merged into master. There were some race issues with one of the sstate performance improvements but that is now resolved as far as I know. We're making slow/steady progress on gcc 4.8.
1.5 planning is well underway now and some people are starting to work on the implementation of features.
1.4.1
=====
Paul is going to maintain the 1.4 series. He's already queued up several of the fixes that didn't make 1.4 and these are now undergoing testing on the autobuilder. If anyone has any changes to propose for 1.4.1, now is the time. We're not looking at features or upgrades but will consider bug fixes.
1.3.2
=====
I've merged a lot of queued changes that Ross prepared for 1.3.2 and this is now undergoing testing.
Python 3
========
I've been asked when bitbake will work under python3 several times now. The first question is which python 3 as there are big differences between them. I'm still not sure which python 3.X we'd end up wanting to target.
I've done a bit of research and the changes we need to make are mostly of the annoying kind. I have had bitbake build a few things (e.g. pseudo-native) with a hacked up bitbake and metadata. The current roadblock is the oe.types functionality and I think I'll need Chris' help to fix this since some functionality it relies on was removed in 3.x.
I've a series I'll send out which deals with the simple issues.
There are several cases we'll have to put in "hacky" code to make things work for both py2 and py3, the most annoying being octal file permissions. There is no syntax which works in both so we're facing having to write them in hexidecimal if we want both to work. When I have spare time I'll continue to work on it and try and get a more complete build working.
Cheers,
Richard
Quoted 5 lines · Richard Purdie
1.3.2
=====I've merged a lot of queued changes that Ross prepared for 1.3.2 and this is now undergoing testing.
I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile on openSuSE 12.3 (which, apparently, is also affected by the same (or a similar) DSO linking change that affects fedora). Are the queued changes available somewhere so I can check this hasn't already been applied?
Quoted 11 lines · Trevor Woerner
Quoted 5 lines
1.3.2
=====I've merged a lot of queued changes that Ross prepared for 1.3.2 and this is now undergoing testing.
I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile on openSuSE 12.3 (which, apparently, is also affected by the same (or a similar) DSO linking change that affects fedora). Are the queued changes available somewhere so I can check this hasn't already been applied?
The merged changes are in the "danny" branch of the oe-core and poky, and there's a ross/danny-next branch in openembedded-core-contrib that is my staging area for submissions to danny.
Ross
Quoted 9 lines · Ross
Quoted 5 lines
I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile on openSuSE 12.3 (which, apparently, is also affected by the same (or a similar) DSO linking change that affects fedora). Are the queued changes available somewhere so I can check this hasn't already been applied?
The merged changes are in the "danny" branch of the oe-core and poky, and there's a ross/danny-next branch in openembedded-core-contrib that is my staging area for submissions to danny.
I've looked through the list of patches and don't seem to find anything that will do what my patch needs to do in order to build qemu-1.2.0 on openSuSE 12.3. Would you consider adding the attached patch for Danny? (normally I'd send it in-line but I'm behind a firewall at the moment that won't allow "git send-email" to succeed, otherwise I could submit it this evening)
From a4ada65e68cece477ef760995ae3395cc7dd27f8 Mon Sep 17 00:00:00 2001
From: Trevor Woerner <[email protected]>
Date: Tue, 7 May 2013 13:37:14 -0400
Subject: [PATCH][danny] qemu-native: fix DSO linking
I noticed this issue trying to build using the Danny branch on what is currently the most recent openSuSE (12.3). It appears to be similar to the fedora DSO linking issue:
https://fedoraproject.org/wiki/UnderstandingDSOLinkChange.
Upstream-status: Inappropriate [OE Specific]
--- .../qemu/qemu-1.2.0/linker-flags-2.patch | 26 ++++++++++++++++++++ meta/recipes-devtools/qemu/qemu_1.2.0.bb | 1 + 2 files changed, 27 insertions(+) create mode 100644 meta/recipes-devtools/qemu/qemu-1.2.0/linker-flags-2.patch
meta/recipes-devtools/qemu/qemu-1.2.0/linker-flags-2.patch new file +26 -0
@@ -0,0 +1,26 @@ +diff -urN qemu-1.2.0.orig/Makefile qemu-1.2.0/Makefile +--- qemu-1.2.0.orig/Makefile 2012-09-05 10:03:06.000000000 -0400 ++++ qemu-1.2.0/Makefile 2013-05-07 12:18:23.638560591 -0400 +@@ -172,7 +172,7 @@ + qemu-img-cmds.h: $(SRC_PATH)/qemu-img-cmds.hx + $(call quiet-command,sh $(SRC_PATH)/scripts/hxtool -h < $< > $@," GEN $@") + +-qemu-ga$(EXESUF): LIBS = $(LIBS_QGA) ++qemu-ga$(EXESUF): LIBS = $(LIBS_QGA) -lrt + qemu-ga$(EXESUF): QEMU_CFLAGS += -I qga/qapi-generated + + gen-out-type = $(subst .,-,$(suffix $@)) +diff -urN qemu-1.2.0.orig/configure qemu-1.2.0/configure +--- qemu-1.2.0.orig/configure 2012-09-05 10:03:06.000000000 -0400 ++++ qemu-1.2.0/configure 2013-05-07 12:11:06.940307455 -0400 +@@ -2681,6 +2681,10 @@ + LIBS="-lrt $LIBS" + fi + ++if test "$linux" = "yes" ; then ++ LIBS="-lrt $LIBS" ++fi ++ + if test "$darwin" != "yes" -a "$mingw32" != "yes" -a "$solaris" != yes -a \ + "$aix" != "yes" -a "$haiku" != "yes" ; then + libs_softmmu="-lutil $libs_softmmu"
meta/recipes-devtools/qemu/qemu_1.2.0.bb +1 -0
@@ -8,6 +8,7 @@ SRC_URI = "\ file://powerpc_rom.bin \ file://no-strip.patch \ file://linker-flags.patch \ + file://linker-flags-2.patch \ file://qemu-vmware-vga-depth.patch \ file://fix-configure-checks.patch \ file://fallback-to-safe-mmap_min_addr.patch \
Signature · 1 line
1.7.10.GIT
Burton, Ross
AppliedQuoted 6 lines · Trevor Woerner
I've looked through the list of patches and don't seem to find anything that will do what my patch needs to do in order to build qemu-1.2.0 on openSuSE 12.3. Would you consider adding the attached patch for Danny? (normally I'd send it in-line but I'm behind a firewall at the moment that won't allow "git send-email" to succeed, otherwise I could submit it this evening)
Merged to my danny-next branch, after confirming that this isn't needed in Dylan/master as qemu 1.4 has the -lrt linkages declared.
Ross
Quoted 10 lines · Ross
Quoted 6 lines · Trevor Woerner
I've looked through the list of patches and don't seem to find anything that will do what my patch needs to do in order to build qemu-1.2.0 on openSuSE 12.3. Would you consider adding the attached patch for Danny? (normally I'd send it in-line but I'm behind a firewall at the moment that won't allow "git send-email" to succeed, otherwise I could submit it this evening)
Merged to my danny-next branch, after confirming that this isn't needed in Dylan/master as qemu 1.4 has the -lrt linkages declared.
Whoops, sorry. I guess I should have mentioned that (since I was aware that qemu-native works fine with the latest Yocto HEAD).