RSS/Atom feed Twitter
Site is read-only, email is disabled

Fwd: self-compiled git gimp 2.9 complains about old babl version

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

4 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

Fwd: self-compiled git gimp 2.9 complains about old babl version trapDoor 29 Jul 10:39
  Fwd: self-compiled git gimp 2.9 complains about old babl version Guiu Rocafort 29 Jul 10:47
   Fwd: self-compiled git gimp 2.9 complains about old babl version trapDoor 29 Jul 12:24
   Fwd: self-compiled git gimp 2.9 complains about old babl version Kevin Cozens 29 Jul 15:24
trapDoor
2012-07-29 10:39:00 UTC (over 12 years ago)

Fwd: self-compiled git gimp 2.9 complains about old babl version

forgot to cc the gimp-developer ml..

---------- Forwarded message ---------- From: trapDoor
Date: Sun, Jul 29, 2012 at 12:34 PM
Subject: Re: [Gimp-developer] self-compiled git gimp 2.9 complains about old babl version
To: Guiu Rocafort

Hi,
did you compile manually babl (and gegl) before compiling gimp? That's the best way to build the whole 'gimp environment' cause you get not only fresh gimp but also its crucial dependencies. This matters especially when you work on the gimp master branch, where many new features will depend on recent commits in babl and gegl. Just remove any instllations of babl and gegl and then build babl, gegl and gimp respectively.

Regards
Tomasz

On Sat, Jul 28, 2012 at 11:54 PM, Guiu Rocafort wrote:

I've been making my first attempt to compile gimp. I've compiled babl and gegl both from git. When compiling gimp ( also from git ) it compiles successfully but when executing it it complains about having an old version of babl. I'm sure I have the latest babl version because I've compiled it from git and i actually made a "make install" on it so the babl gimp is taking should be the one I compiled. Any idea about what can be wrong ?

The exact error message says like this:

"BABL version too old!

GIMP requires BABL version 0.1.11 or later. Installed BABL version is 0.1.10.

Somehow you or your software packager managed to install GIMP with an older BABL version.

Please upgrade to BABL version 0.1.11 or later."

Thanks in advance Guiu Rocafort

--
Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Guiu Rocafort
2012-07-29 10:47:15 UTC (over 12 years ago)

Fwd: self-compiled git gimp 2.9 complains about old babl version

Hi,
did you compile manually babl (and gegl) before compiling gimp? That's the best way to build the whole 'gimp environment' cause you get not only fresh gimp but also its crucial dependencies.

Yes, I've compiled them myself. Both of them were taken from the git repository directly.I also made an "sudo make install" to install them on the system after compiling because I thought it would be easier for gimp to find the babl and gegl version I've compiled.

It seems like having made a compiling from git and an "sudo make install" installed the new versions of babl and gegl, but the package manager doesn't noticed that and still thinks i have the previous version installed. Does that make sense ? Any idea of how to fix that ?

Cheers Guiu Rocafort

On Sun, Jul 29, 2012 at 12:39 PM, trapDoor wrote:

forgot to cc the gimp-developer ml..

---------- Forwarded message ---------- From: trapDoor
Date: Sun, Jul 29, 2012 at 12:34 PM
Subject: Re: [Gimp-developer] self-compiled git gimp 2.9 complains about old babl version
To: Guiu Rocafort

Hi,
did you compile manually babl (and gegl) before compiling gimp? That's the best way to build the whole 'gimp environment' cause you get not only fresh gimp but also its crucial dependencies. This matters especially when you work on the gimp master branch, where many new features will depend on recent commits in babl and gegl. Just remove any instllations of babl and gegl and then build babl, gegl and gimp respectively.

Regards
Tomasz

On Sat, Jul 28, 2012 at 11:54 PM, Guiu Rocafort wrote:

I've been making my first attempt to compile gimp. I've compiled babl and gegl both from git. When compiling gimp ( also from git ) it compiles successfully but when executing it it complains about having an old

version

of babl. I'm sure I have the latest babl version because I've compiled it from git and i actually made a "make install" on it so the babl gimp is taking should be the one I compiled. Any idea about what can be wrong ?

The exact error message says like this:

"BABL version too old!

GIMP requires BABL version 0.1.11 or later. Installed BABL version is 0.1.10.

Somehow you or your software packager managed to install GIMP with an older BABL version.

Please upgrade to BABL version 0.1.11 or later."

Thanks in advance Guiu Rocafort

--
Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

trapDoor
2012-07-29 12:24:40 UTC (over 12 years ago)

Fwd: self-compiled git gimp 2.9 complains about old babl version

Whatever distro you work on, the package manager won't notice your installation if you made it by 'make install' in the project's source code. The package manager will see only applications installed as packages (eg deb on debian/ubuntu/mint or rpm on fefora/centos etc). Now if you still see old babl in the package manager it probably means that you didn't remove it before building your version. If you installed your built in the same directory as the one installed from the package your pkg manager still will not notice any version change. If you chose different directory for your custom installation then you will end up with two versions of babl and then i'm not sure where gimp/gegl will look for babl first. They may pick not the version you want (it also depends of your configuration of babl, gegl and gimp before building them).

On Sun, Jul 29, 2012 at 12:47 PM, Guiu Rocafort wrote:

Hi,
did you compile manually babl (and gegl) before compiling gimp? That's the best way to build the whole 'gimp environment' cause you get not only fresh gimp but also its crucial dependencies.

Yes, I've compiled them myself. Both of them were taken from the git repository directly.I also made an "sudo make install" to install them on the system after compiling because I thought it would be easier for gimp to find the babl and gegl version I've compiled.

It seems like having made a compiling from git and an "sudo make install" installed the new versions of babl and gegl, but the package manager doesn't noticed that and still thinks i have the previous version installed. Does that make sense ? Any idea of how to fix that ?

Cheers Guiu Rocafort

On Sun, Jul 29, 2012 at 12:39 PM, trapDoor wrote:

forgot to cc the gimp-developer ml..

---------- Forwarded message ---------- From: trapDoor
Date: Sun, Jul 29, 2012 at 12:34 PM
Subject: Re: [Gimp-developer] self-compiled git gimp 2.9 complains about old babl version
To: Guiu Rocafort

Hi,
did you compile manually babl (and gegl) before compiling gimp? That's the best way to build the whole 'gimp environment' cause you get not only fresh gimp but also its crucial dependencies. This matters especially when you work on the gimp master branch, where many new features will depend on recent commits in babl and gegl. Just remove any instllations of babl and gegl and then build babl, gegl and gimp respectively.

Regards
Tomasz

On Sat, Jul 28, 2012 at 11:54 PM, Guiu Rocafort wrote:

I've been making my first attempt to compile gimp. I've compiled babl and
gegl both from git. When compiling gimp ( also from git ) it compiles successfully but when executing it it complains about having an old version
of babl. I'm sure I have the latest babl version because I've compiled it
from git and i actually made a "make install" on it so the babl gimp is taking should be the one I compiled. Any idea about what can be wrong ?

The exact error message says like this:

"BABL version too old!

GIMP requires BABL version 0.1.11 or later. Installed BABL version is 0.1.10.

Somehow you or your software packager managed to install GIMP with an older BABL version.

Please upgrade to BABL version 0.1.11 or later."

Thanks in advance Guiu Rocafort

--
Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

--
Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

Kevin Cozens
2012-07-29 15:24:23 UTC (over 12 years ago)

Fwd: self-compiled git gimp 2.9 complains about old babl version

On 12-07-29 06:47 AM, Guiu Rocafort wrote:

It seems like having made a compiling from git and an "sudo make install" installed the new versions of babl and gegl, but the package manager doesn't noticed that and still thinks i have the previous version installed. Does that make sense ? Any idea of how to fix that ?

You can use the command "pkg-config --modversion babl" to check what version of BABL the package manager is finding. Its possible the package manager is finding the right package but the linker might not be. On some systems you might need to run ldconfig after installing a package. Its often done automatically as part of the install process but sometimes its not.