Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] gdk-pixbuf: convert from autotools to meson
Date: Fri, 01 Mar 2019 20:15:12 +0100	[thread overview]
Message-ID: <1b9a376930ad3463214f725bc203a357@agner.ch> (raw)
In-Reply-To: <6378eef56d799e4b91da708cc8fff92c0e4bc13e.camel@linuxfoundation.org>

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@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
...

--
Stefan


  parent reply	other threads:[~2019-03-01 19:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 20:10 [PATCH 1/4] pango: convert from autotools to meson Alexander Kanavin
2019-02-20 20:10 ` [PATCH 2/4] llvm: switch to the official git repository Alexander Kanavin
2019-02-20 20:10 ` [PATCH 3/4] gdk-pixbuf: convert from autotools to meson Alexander Kanavin
2019-02-22 10:18   ` Burton, Ross
2019-02-22 13:12     ` Alexander Kanavin
2019-02-23 12:29   ` Richard Purdie
2019-02-23 12:41     ` Alexander Kanavin
2019-02-23 12:42     ` Richard Purdie
2019-02-23 12:51       ` Alexander Kanavin
2019-02-23 13:25         ` Richard Purdie
2019-02-23 13:36           ` Richard Purdie
2019-02-23 13:43             ` Alexander Kanavin
2019-02-23 13:46               ` Richard Purdie
2019-03-01 19:15     ` Stefan Agner [this message]
2019-03-01 23:00       ` Stefan Agner
2019-02-20 20:10 ` [PATCH 4/4] glib-2.0: " Alexander Kanavin
2019-02-22 10:20   ` Burton, Ross
  -- strict thread matches above, loose matches on Subject: below --
2019-02-20 13:50 [PATCH 1/4] pango: " Alexander Kanavin
2019-02-20 13:50 ` [PATCH 3/4] gdk-pixbuf: " Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1b9a376930ad3463214f725bc203a357@agner.ch \
    --to=stefan@agner.ch \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox