Where Is Glib-devl X86-64?

Home » CentOS » Where Is Glib-devl X86-64?
CentOS 8 Comments

I have a brand new installation of Rocky Linux 9.1 (I know, this isn’t a Rocky mailing list, but I can’t find anything on this on Rocky forums, etc. so I figured I would ask here), and I installed Gimp, and would like to install the Resynthesizer plugin package.

Trying to compile it from source, autogen.sh complains that I don’t have the gimp development libraries installed. In fact, I can’t find glib-devel anywhere in any of the configured repos (all the default Rocky repos, epel, rpmfusion).

Rocky is shipping an unstable development version of Gimp, so maybe they haven’t made glib-devel available yet ???

Thanks in advance for any help you can give!

Fred

8 thoughts on - Where Is Glib-devl X86-64?

  • well, I’m still confused.

    sudo dnf install glib2-devel says it is already installed.

    running autogen.sh for resynthesizer outputs:

    $ ./autogen.sh

    I am testing that you have the required versions of autoconf, automake, glib-gettextize and intltoolize…

    checking for autoconf >= 2.54 … yes (version 2.69)
    checking for automake >= 1.6 … yes (version 1.16.2)
    checking for glib-gettextize >= 2.0.0 … yes (version 2.68.4)
    checking for intltool >= 0.17 … yes (version 0.51.0)

    I am going to run ./configure with the following arguments:

    –enable-maintainer-mode

    If you wish to pass additional arguments, please specify them on the ./autogen.sh command line or set the AUTOGEN_CONFIGURE_ARGS
    environment variable.

    Copying file po/Makefile.in.in

    Please add the files
    codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
    progtest.m4
    from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/.

    checking for a BSD-compatible install… /usr/bin/install -c checking whether build environment is sane… yes checking for a thread-safe mkdir -p… /usr/bin/mkdir -p checking for gawk… gawk checking whether make sets $(MAKE)… yes checking whether make supports nested variables… yes checking whether make supports the include directive… yes (GNU style)
    checking for gcc… gcc checking whether the C compiler works… yes checking for C compiler default output file name… a.out checking for suffix of executables… checking whether we are cross compiling… no checking for suffix of object files… o checking whether we are using the GNU C compiler… yes checking whether gcc accepts -g… yes checking for gcc option to accept ISO C89… none needed checking whether gcc understands -c and -o together… yes checking dependency style of gcc… gcc3
    checking for library containing strerror… none required checking for gcc… (cached) gcc checking whether we are using the GNU C compiler… (cached) yes checking whether gcc accepts -g… (cached) yes checking for gcc option to accept ISO C89… (cached) none needed checking whether gcc understands -c and -o together… (cached) yes checking dependency style of gcc… (cached) gcc3
    checking for gcc… (cached) gcc checking whether we are using the GNU C compiler… (cached) yes checking whether gcc accepts -g… (cached) yes checking for gcc option to accept ISO C89… (cached) none needed checking whether gcc understands -c and -o together… (cached) yes checking dependency style of gcc… (cached) gcc3
    checking how to run the C preprocessor… gcc -E
    checking for grep that handles long lines and -e… /usr/bin/grep checking for egrep… /usr/bin/grep -E
    checking for ANSI C header files… yes checking whether to enable maintainer-specific portions of Makefiles… yes checking for pkg-config… /usr/bin/pkg-config checking pkg-config is at least version 0.9.0… yes checking for GIMP… no configure: error: *GIMP development libraries not found*; please install.

    Configure failed or did not finish!

    clearly I’m not smart enough to figure this out. one of you smart people feel like offering further advice?

    PS:
    oh, there is also a glib2.pc file in /usr/lib64/pkgconfig.

    $ ls -l /usr/lib64/pkgconfig/glib-2*
    -rw-r–r–. 1 root root 444 May 16 2022 /usr/lib64/pkgconfig/glib-2.0.pc

    cat /usr/lib64/pkgconfig/glib-2.0.pc:

    prefix=/usr libdir=${prefix}/lib64
    includedir=${prefix}/include

    bindir=${prefix}/bin glib_genmarshal=${bindir}/glib-genmarshal gobject_query=${bindir}/gobject-query glib_mkenums=${bindir}/glib-mkenums

    Name: GLib Description: C Utility Library Version: 2.68.4
    Requires.private: libpcre >= 8.31, sysprof-capture-4 >= 3.38.0
    Libs: -L${libdir} -lglib-2.0
    Libs.private: -pthread -lm Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include

  • I have gimp installed on AlmaLinux 9 here which has RPMs:
    gimp-libs-2.99.8-3.el9.x86_64
    gimp-2.99.8-3.el9.x86_64.

    I would look at the generated configure file and config.log to see what it’s really looking for.

    Bill

  • I don’t have right now a Rocky Linux 9.x system at hand, but from what I’ve seen, you should install the gimp-devel-tools package

    $ rpm -qpi ./gimp-devel-tools-2.99.8-3.el9.x86_64.rpm warning: ./gimp-devel-tools-2.99.8-3.el9.x86_64.rpm: Header V4 RSA/SHA256
    Signature, key ID 350d275d: NOKEY
    Name : gimp-devel-tools Epoch : 2
    Version : 2.99.8
    Release : 3.el9
    Architecture: x86_64
    Install Date: (not installed)
    Group : Unspecified Size : 26612
    License : LGPLv3+
    Signature : RSA/SHA256, Mon 31 Oct 2022 10:56:19 PM CET, Key ID
    702d426d350d275d Source RPM : gimp-2.99.8-3.el9.src.rpm Build Date : Mon 31 Oct 2022 10:34:33 PM CET
    Build Host : pb-9e56c5ea-a265-4012-a7b6-4abde563b600-b-x86-64
    Packager : Rocky Linux Build System (Peridot)
    Vendor : Rocky Enterprise Software Foundation URL : http://www.gimp.org/
    Summary : GIMP plugin and extension development tools Description :
    The gimp-devel-tools package contains gimptool, a helper program to build GNU Image Manipulation Program (GIMP) plug-ins and extensions.

    Have you already installed it? Can you try in case and then re-run the autogen.sh?

    HIH, Gianluca

  • Am 21.03.23 um 23:10 schrieb Fred:

    I think you will get more trouble because this plugin uses python2 code and I am not sure if this is supported under EL9.

    You could try the flatpak version of this plugin …

    $ flatpak remote-add –user –if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

    $ flatpak –user install Resynthesizer org.gimp.GIMP