On 22/03/2018 13:07, Ryan Marsaw wrote: > On Thu, 22 Mar 2018, [email protected] wrote: > >>> Did you install gdk-pixbuf using the Meson build system by any chance? If >>> so, did you >>> issue the following afterwards (as root user)? >>> gdk-pixbuf-query-loaders --update-cache >>> I remember a while back when I first built gdk-pixbuf with Meson I >>> received a build error in one of the packages that followed. I forget >>> which package it was, but I think it may have had something to do with >>> what you're experiencing. I _think_. >> >> I also tried to build gdk-pixbuf (2.36.11) with glib (2.56.0) but I got the >> same error message "Couldn't recognize the image file format for >> file " when I tried to build GTK+2. >> >> If you check the meson_options.txt for the package "gdk-pixbuf", you can >> find an option "builtin_loaders" and the default value is "none". >> >> However, even you set it to "all" and all loaders are built sucessfully (You >> can use "gdk-pixbuf-query-loaders" command for checking), the error message >> still exits. >> >> On the other hand, even the loader is not built, the application >> "gdk-pixbuf-csource" will link to the "libpng" directly. (You can use ldd >> command to check it). But, it won't help you to fix the error message. >> ("gdk-pixbuf-csource" still gives nothing when it try to load any png file.) >> >> So, my current solution is: use the old version (2.54.3) of glib for my BLFS >> system. >> -- > > I was able to reproduce the GTK2 build error by removing the > "shared-mime-info" package before building GTK2. In my BLFS build I > install shared-mime-info just before installing gdk-pixbuf. I also > install gdk-pixbuf using Meson, which is not the build system used for > that package in BLFS. I don't know if that makes any difference. I'm > assuming you've installed shared-mime-info because it is a required > dependency of gdk-pixbuf. >
Yes, I had that... No, really: the problem was with the glib-2.56.0 instructions from March 18th, after removal of the "meson-fixes" patch. I you have a glib with the patch (provided it applies), I guess it addresses the problem I was seeing (glib-2.54.3 with the patch had no problem). But now, back with autotools, looks like everything is fine with glib-2.56.0. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
