[OE-core] [PATCH 3/4] gdk-pixbuf: convert from autotools to meson

[Stefan Agner]

On 01.03.2019 20:15, Stefan Agner wrote:
> On 23.02.2019 13:29, Richard Purdie wrote:
>> On Wed, 2019-02-20 at 21:10 +0100, Alexander Kanavin wrote:
>>> Drop autotools-specific patches.
>>>
>>> Rework jku's thumbnailer patch into meson configuration.
>>>
>>> Signed-off-by: Alexander Kanavin <alex.kanavin at gmail.com>
>>
>> We've seen it before but its happened again:
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/326
>>
>> I went into the failed build directory and ran "bitbake core-image-sato
>> -c testsdkext" and it succeeded so I'm not sure sure how we're going to
>> debug this one...
> 
> I am not sure if it is related, but we see psplash failing with a custom
> png recently.
> 
> failed to load ".../splashscreen-blue.png": Couldn’t recognize the image
> file format for file “.../splashscreen-blue.png”
> 
> The psplash calls gdk-pixbuf-csource (through make-image-header.sh). We
> only saw it failing when building in a Ubuntu 18.04 container, but then
> reproducible.
> 
> I also noticed this (probably unrelated) in do_configure log:
> 
> DEBUG: Executing shell function do_configure
> gtkdocize: neither configure.ac nor configure.in exist
> NOTE: Executing meson -Denable_jpeg=true -Denable_jasper=false
> -Denable_png=true -Denable_tiff=false -Dx11=false
> -Dinstalled_tests=false...
> The Meson build system
> Version: 0.49.2
> Source dir:
> /workdir/oe/tmp/work/x86_64-linux/gdk-pixbuf-native/2.38.0-r0/gdk-pixbuf-2.38.0
> Build dir:
> /workdir/oe/tmp/work/x86_64-linux/gdk-pixbuf-native/2.38.0-r0/build
> Build type: native build
> WARNING: Unknown options: "enable_jasper, enable_jpeg, enable_png,
> enable_tiff
> ...

FWIW, I sent a patch to fix this particular warning just above. However,
my issue persists.

The problem is definitly gdk-pixbuf related, but reverting the two
patches from this patchset did not resolve the issue.

--
Stefan