Am Donnerstag, 8. Oktober 2015, 10:57:49 schrieb Sam Gleske:
It's likely that you're missing LD_LIBRARY_PATH when you're loading GIMP. While you're starting GIMP that was compiled from Git it is loading GEGL libraries from other sources. You should do the following (assuming GIMP, GEGL, and BABL were installed under /usr/local prefix by default): LD_LIBRARY_PATH=/usr/local/lib gimp-2.9 GIMP will then look to /usr/local/lib for its GEGL and BABL libraries instead of /usr/lib (which is where it is typically installed by a package manager).
With everyone telling how they build GIMP I would like to add how to avoid setting the LD_LIBRARY_PATH: baking the path into the executable. I am installing everything (babl, gegl and GIMP) to /opt/gimp-GIT/ (which belongs to my user so I don't need root to install). These are my calls to configure the three, afterwards a simple "make -j5 install" is enough. babl: LDFLAGS="-Wl,-rpath -Wl,/opt/gimp-GIT/lib" CFLAGS="-march=native -O3" CXXFLAGS="$CFLAGS" ./autogen.sh --prefix=/opt/gimp-GIT/ gegl (disabling stuff just because I don't need it): PKG_CONFIG_PATH="/opt/gimp-GIT/lib/pkgconfig" LDFLAGS="-Wl,-rpath - Wl,/opt/gimp-GIT/lib" CFLAGS="-march=native -O3" CXXFLAGS="$CFLAGS" ./autogen.sh --prefix=/opt/gimp-GIT/ --disable-docs --without-libavformat -- without-vala GIMP (with mypaint being installed in /opt/mypaint/): PKG_CONFIG_PATH="/opt/gimp-GIT/lib/pkgconfig:/opt/mypaint/lib/pkgconfig" LDFLAGS="-Wl,-rpath -Wl,/opt/gimp-GIT/lib" CFLAGS="-march=native -O3" CXXFLAGS="$CFLAGS" ./autogen.sh --prefix=/opt/gimp-GIT --enable-python Each of them is one line. HTH Tobias
On Wed, Oct 7, 2015 at 11:31 PM, Olivier <olecarme gmail com> wrote:In fact, I also built glib from git, thus maybe GIO_EXTRA_MODULES was also needed. Anyway, I used it and everything is OK now. Olivier Lecarme 2015-10-07 21:23 GMT+02:00 Elle Stone <ellestone ninedegreesbelow com>:On 10/07/2015 12:54 PM, Olivier wrote:Finally I succedded in installing GIMP, by fetching gegl, babl, gdk-pixbuf, and gimp itself from git, and configuring and installing them all under the same prefix. Under Ubuntu 15.04, the GIO extra modules are located in usr/lib/x86_64-linux-gnu/gio/modules. Thus I used Martin Nordholts' explanation in http://www.gimp.org/source/howtos/gimp-git-build.html, but I addedgegl,babl, and gdk-pixbuf tothe packages to be fetched from git, compiled and installed, and I added GIO_EXTRA_MODULES to the exported variables, although I'm not sure that is needed. Thanks to all! Olivier LecarmeBased on comments in https://aur.archlinux.org/packages/gegl-git/, it does look like maybe the original problem was that GIMP was finding a too-outdated version of GEGL. I never needed to export GIO_EXTRA_MODULES until I tried to run GIMP 2.8 installed from the Gentoo package manager alongside babl/GEGL/GIMP fromgitinstalled in a prefix. But here's the reference, fwiw:https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00042 .html https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00051 .html>Looking at what Mitch said, it seems exporting GIO_EXTRA_MODULES is only be needed if glib is also built in the prefix. So sorry for the noise! if you didn't also build glib in the prefix. For the next person trying to build GIMP from git who might stumble over this thread, a few other "why it doesn't work and what to do" are documented here: http://wiki.gimp.org/wiki/Hacking:Problems_and_solutions-- Olivier Lecarme _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list gnome org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Attachment:
signature.asc
Description: This is a digitally signed message part.