Re: [OE-core] [PATCH 0/6] Upgrades: GLib & friends

2015-11-09 Thread Burton, Ross
On 8 November 2015 at 10:19, Jussi Kukkonen wrote: > Alternatively, moving to qemu 2.4.1 (that was released this week) will > solve the issue as well. > Sounds good. Can you add a patch to the current qemu and we can drop it if a tested qemu upgrade also gets merged.

Re: [OE-core] [PATCH 0/6] Upgrades: GLib & friends

2015-11-08 Thread Jussi Kukkonen
On 6 November 2015 at 22:38, Burton, Ross wrote: > > On 5 November 2015 at 13:27, Jussi Kukkonen > wrote: > >> This should be a cosmetic issue (as custom allocators didn't >> really work before either) and is already fixed in upstream Qemu. >> >

Re: [OE-core] [PATCH 0/6] Upgrades: GLib & friends

2015-11-06 Thread Burton, Ross
On 5 November 2015 at 13:27, Jussi Kukkonen wrote: > This should be a cosmetic issue (as custom allocators didn't > really work before either) and is already fixed in upstream Qemu. > As this is pretty ugly, can we backport the fix to our qemu? Ross --

[OE-core] [PATCH 0/6] Upgrades: GLib & friends

2015-11-05 Thread Jussi Kukkonen
GLib 2.46 made custem memory allocation functions no-ops: This leads to a warning "custom memory allocation vtable not supported" on Qemu startup. This should be a cosmetic issue (as custom allocators didn't really work before either) and is already fixed in upstream Qemu. The following changes