On 10/14/20 10:50 PM, DJ Lucas - LFS via blfs-support wrote:
Being that nobody is reporting it, I'm guessing not, but I'll ask anyway. Has anybody had issues building gkd-pixbuf-2.40.0? From a related bug report, it looks like some missing dependency elsewhere. It really doesn't matter much as libpng is runtime, but the tests are unable to be compiled here:

Message:
GDK-Pixbuf 2.40.0
==================
            prefix: /usr
            libdir: /usr/lib
           datadir: /usr/share
        libexecdir: /usr/libexec

   enabled loaders: png jpeg tiff

     documentation: false
         man pages: true
     introspection: true
               x11: true
   installed tests: true
       relocatable: false

Build targets in project: 86

<snip>

[151/176] Generating loaders.cache with a meson_exe.py custom command
[152/176] Linking target thumbnailer/gdk-pixbuf-print-mime-types
[153/176] Linking target tests/pixbuf-read
[154/176] Generating resources.c with a custom command
failed to load "/home/pkguser/Main/gdk-pixbuf/src/gdk-pixbuf-2.40.0/tests/icc-profile.png": Couldn?t recognize the image file format for file ?/home/pkguser/Main/gdk-pixbuf/src/gdk-pixbuf-2.40.0/tests/icc-profile.png?
../tests/resources.gresource.xml: Child process exited with code 1.
[155/176] Compiling C object contrib/gdk-pixbuf-xlib/libgdk_pixbuf_xlib-2.0.so.0.4000.0.p/gdk-pixbuf-xlibrgb.c.o
[156/176] Generating resources.h with a custom command
failed to load "/home/pkguser/Main/gdk-pixbuf/src/gdk-pixbuf-2.40.0/tests/icc-profile.png": Couldn?t recognize the image file format for file ?/home/pkguser/Main/gdk-pixbuf/src/gdk-pixbuf-2.40.0/tests/icc-profile.png?
../tests/resources.gresource.xml: Child process exited with code 1.

Here may be a partial fix, but I don't entirely understand the comments in the bug report, looks like something misisng in gobject-introspection?
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/123
​​​​​​
Patch is here:
​​​​​ https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/commit/7f0b214ad921c0ad00ff4ef57b531a6f18f7ccc9

I simply worked around it by killing off the tests with a more direct method: sed "/  subdir('tests')/d" -i meson.build
May be an entirely me issue, but something is off. Any ideas?

The tests were clean for me. I did not get the messages above. The issue you mention talks about -Dpng=false which we do not use.

The messages and the step numbers differed from what I had, but that may just be an artifact of ninja and multiple cores.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to