On Saturday 18 July 2009 08:54:14 pm Greg S. wrote:

Hi, when I use ./configure the message says at the end that can't find babl

checking for BABL... configure: error: Package requirements (babl

= 0.1.0) were not met:

No package 'babl' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.

does anyone have any suggestions please.

You have to download, compile (?) and install the latest versions of babl and gegl. It is a royal pain but once it is done you are set for several upgrades, until Gimp requires a newer version. IMO these required libraries should be embedded in the Gimp release itself but there may be turf issues that prevent that.

John Culleton wrote:

IMO these required libraries should be embedded in the Gimp release itself but there may be turf issues that prevent that.

You aren't really serious about this, right?

Michael

Greg S. wrote:

Hi, i have already installed babl and gegl but still no good when using ./configure This is driving me nuts.

What about the

"Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix."

part? If you need help to understand this one you should say so, otherwise people will assume that you are actually doing what it suggests.

HTH, Michael

Greg S. wrote:

Hi, i have already installed babl and gegl but still no good when using
./configure This is driving me nuts.

What about the

"Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix."

part? If you need help to understand this one you should say so, otherwise people will assume that you are actually doing what it suggests.

HTH,
Michael

Yes I need all the help I can get. Please advise me how to do this.

PKG_CONFIG_PATH what am I to do to make this work. Please explain to me like I
am a 5 year old.

You don't say what you are using as an OS, but what you are missing in my mind, are the development files for gegl and babl

if you built babl and gegl from scratch, no problems, but sounds like you might be using Ubuntu or fedora. So look in you package manager for things like gegl-dev and babl-dev

If you built babl and gegl in some non standard directory, you need to tell the system where to find them, hence;

export PKG_CONFIG_PATH=/non_standard/directory/lib/pkgconfig

hth

Greg S. wrote:

Hi, i have already installed babl and gegl but still no good when using
./configure This is driving me nuts.

What about the

"Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix."

part? If you need help to understand this one you should say so, otherwise people will assume that you are actually doing what it suggests.

HTH,
Michael

Yes I need all the help I can get. Please advise me how to do this.

PKG_CONFIG_PATH what am I to do to make this work. Please explain to
me like I
am a 5 year old.

You don't say what you are using as an OS, but what you are missing in
my mind, are the development files for gegl and babl

if you built babl and gegl from scratch, no problems, but sounds like you might be using Ubuntu or fedora. So look in you package manager for things like gegl-dev and babl-dev

If you built babl and gegl in some non standard directory, you need to
tell the system where to find them, hence;

export PKG_CONFIG_PATH=/non_standard/directory/lib/pkgconfig

hth

I am using Centos 5.3

And does Centos have a package manager?

On 07/19/2009 03:16 AM, John Culleton wrote: > IMO

these required libraries should be embedded in the Gimp release itself but there may be turf issues that prevent that.

Embedding babl and GEGL in the GIMP tarball would make usage of GEGL by other projects much more complicated, and we don't want that. A library shared between many apps will have much more development and maintenance than a library only used by a single app, so we should encourage usage of these libraries by other projects.

/ Martin

On 07/19/2009 04:58 AM, Owen wrote:

if you built babl and gegl from scratch, no problems, but sounds like you might be using Ubuntu or fedora. So look in you package manager for things like gegl-dev and babl-dev

If he is trying to build git master then the packages provided by his distro will not work since he basically needs git master of babl and GEGL too.

If you built babl and gegl in some non standard directory, you need to tell the system where to find them, hence;

export PKG_CONFIG_PATH=/non_standard/directory/lib/pkgconfig

There is method to deal with building for non-standard prefixes that is superior to manually managing the environment variables, and this method is config.site.

Put this in the file /home/user/dev/share/config.site:

# for development: export CFLAGS="-g -O0" export PKG_CONFIG_PATH="/home/user/dev/lib/pkgconfig:$PKG_CONFIG_PATH" export LD_LIBRARY_PATH="/home/user/dev/lib:$LD_LIBRARY_PATH"

This file will then be sourced by configure whenever it is invoked with the prefix /home/user/dev, so assuming you have all build dependencies, all you have to do to build babl, GEGL and GIMP is to clone all the repos from git://git.gnome.org/project and then do

./autogen.sh --prefix=/home/user/dev make
make install

in all of them, in that order. Then after git pull --rebase you don't need to bother about setting up the environment again, you just do

make

and all dependencies will be processed properly with the right env vars set.

/ Martin

On 07/19/2009 11:37 AM, Martin Nordholts wrote:

Then after git pull --rebase you don't need to bother about setting up the environment again, you just do

make

That should of course be

make make install

/ Martin

On 07/19/2009 11:39 AM, Martin Nordholts wrote:

On 07/19/2009 11:37 AM, Martin Nordholts wrote:

Then after git pull --rebase you don't need to bother about setting up the environment again, you just do

make

That should of course be

make make install

/ Martin

I should also mention that to run your fresh build of GIMP you don't need to setup any env vars at all since libtool have setup the rpaths in the binaries, so just doing

/home/user/dev/bin/gimp-2.7

without messing with environment variables will launch GIMP 2.7.

/ Martin

Greg S. wrote:

Greg S. wrote:

Hi, i have already installed babl and gegl but still no good when using
./configure This is driving me nuts.

What about the

"Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix."

part? If you need help to understand this one you should say so, otherwise people will assume that you are actually doing what it suggests.

HTH,
Michael

Yes I need all the help I can get. Please advise me how to do this.

PKG_CONFIG_PATH what am I to do to make this work. Please explain to me like I
am a 5 year old.

You don't say what you are using as an OS, but what you are missing in my mind, are the development files for gegl and babl

if you built babl and gegl from scratch, no problems, but sounds like you might be using Ubuntu or fedora. So look in you package manager for things like gegl-dev and babl-dev

If you built babl and gegl in some non standard directory, you need to tell the system where to find them, hence;

export PKG_CONFIG_PATH=/non_standard/directory/lib/pkgconfig

hth

I am using Centos 5.3

This sort of thing comes up continually when installing from tarball.

(1) Is the library/package complained of on your system or not?

(2) If it is, have you got the development package? - you'll need it. Check with your package manager or look for files on your system (typically in /usr) named -devel: without it you can't proceed with compilation. If you haven't, get the development package from somewhere (installation disk, upgrading resource, or Googling for the tarball if necessary.

(3) If you have, where are the libraries for that package installed? commonly /usr/lib or /usr/local/lib, but may be /usr/lib64 or more outlandish places - Find File or equivalent is your friend.

(4) use "echo $PKG_CONFIG_PATH" to see where compilation is going to be looking for external programs - assuming you haven't resolved the problem already by this stage, the libaries you need will be in none of those places.

(5) Use Find File for folders named "pkgconfig" or files ending in ".pc"(no quotes). You'll find quite a number. You should be able to recognise the relevant .pc file for your package amongst the names in the list.
Note which folder it's in, e.g.
"/usr/local/Trolltech/Qt-4.5.2/lib/pkgconfig" (to quote a genuine outlandish example)

(6) Then use the export PKG_CONFIG_PATH before configuring, i.e.

export PKG_CONFIG_PATH=/usr/local/Trolltech/Qt-4.5.2/lib/pkgconfig:$PKG_CONFIG_PATH

(This adds the new path to existing ones. Note: as a general rule *don't* use export PKG_CONFIG_PATH=/non_standard/directory/lib/pkgconfig or you'll completely replace the existing path for this session. You may need the existing path for other progs in the compilation).

/configure

make

(then as root) make install

HTH

Doug

Greg S. wrote:

Greg S. wrote:

Hi, i have already installed babl and gegl but still no good when using
./configure This is driving me nuts.

What about the

"Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix."

part? If you need help to understand this one you should say so, otherwise people will assume that you are actually doing what it suggests.

HTH,
Michael

Yes I need all the help I can get. Please advise me how to do this.

PKG_CONFIG_PATH what am I to do to make this work. Please explain to me like I
am a 5 year old.

You don't say what you are using as an OS, but what you are missing in my mind, are the development files for gegl and babl

if you built babl and gegl from scratch, no problems, but sounds like you might be using Ubuntu or fedora. So look in you package manager for things like gegl-dev and babl-dev

If you built babl and gegl in some non standard directory, you need to tell the system where to find them, hence;

export PKG_CONFIG_PATH=/non_standard/directory/lib/pkgconfig

hth

I am using Centos 5.3

This sort of thing comes up continually when installing from tarball.

(1) Is the library/package complained of on your system or not?

(2) If it is, have you got the development package? - you'll need it. Check with your package manager or look for files on your system (typically in /usr) named -devel: without it you can't proceed with compilation. If you haven't, get the development package from somewhere (installation disk, upgrading resource, or Googling for the tarball if necessary.

(3) If you have, where are the libraries for that package installed? commonly /usr/lib or /usr/local/lib, but may be /usr/lib64 or more outlandish places - Find File or equivalent is your friend.

(4) use "echo $PKG_CONFIG_PATH" to see where compilation is going to be looking for external programs - assuming you haven't resolved the problem already by this stage, the libaries you need will be in none of those places.

(5) Use Find File for folders named "pkgconfig" or files ending in ".pc"(no quotes). You'll find quite a number. You should be able to recognise the relevant .pc file for your package amongst the names in the list.
Note which folder it's in, e.g.
"/usr/local/Trolltech/Qt-4.5.2/lib/pkgconfig" (to quote a genuine outlandish example)

(6) Then use the export PKG_CONFIG_PATH before configuring, i.e.

export PKG_CONFIG_PATH=/usr/local/Trolltech/Qt-4.5.2/lib/pkgconfig:$PKG_CONFIG_PATH

(This adds the new path to existing ones. Note: as a general rule *don't* use export PKG_CONFIG_PATH=/non_standard/directory/lib/pkgconfig or you'll completely replace the existing path for this session. You may need the existing path for other progs in the compilation).

/configure

make

(then as root) make install

HTH

Doug

On 07/20/2009 01:11 AM, Greg S. wrote:

Hi Martin,

Thanks for your info, but git did not work. Other end hungup. Tried many times. Please advise regards

Exactly what commands do you use?

/ Martin

On 07/20/2009 01:22 AM, Greg S. wrote:

On 07/20/2009 01:11 AM, Greg S. wrote:

Hi Martin,

Thanks for your info, but git did not work. Other end hungup. Tried many times. Please advise regards

Exactly what commands do you use?

/ Martin These are the commands to set up git from the git site.

git config --global user.name "Rupert Monkey" git config --global user.email rupert@example.com

Plus below also from git site.

To clone all the history and branches of a project, from a shell:

git clone git://git.gnome.org/[project]

You need to specify the project, try

cd ~/source git clone git://git.gnome.org/babl git clone git://git.gnome.org/gegl git clone git://git.gnome.org/gimp

/ Martin

On 07/20/2009 01:22 AM, Greg S. wrote:

On 07/20/2009 01:11 AM, Greg S. wrote:

Hi Martin,

Thanks for your info, but git did not work. Other end hungup. Tried

many

times. Please advise regards

Exactly what commands do you use?

/ Martin These are the commands to set up git from the git site.

git config --global user.name "Rupert Monkey" git config --global user.email rupert@example.com

Plus below also from git site.

To clone all the history and branches of a project, from a shell:

git clone git://git.gnome.org/[project]

You need to specify the project, try

cd ~/source git clone git://git.gnome.org/babl git clone git://git.gnome.org/gegl git clone git://git.gnome.org/gimp

/ Martin

I put babl, gegl & gimp inside the square brackets it is now cloning repos.

regards

greg

I have all the repos from git for babl, gegl & gimp. I have run ./configure
and still configure can't find babl.

What do I do next. This is driving me nuts. /Greg

Hi,

I will bow out of this for the moment and thank Martin for his build instructions which I will try out.

You might want to look at this,

http://www.gimpusers.com/news/2009-04-23/gimp-master-for-ubuntu-9-04.html

It *really* is that simple

On 07/20/2009 02:05 AM, Greg S. wrote:

I have all the repos from git for babl, gegl& gimp. I have run ./configure and still configure can't find babl.

What do I do next. This is driving me nuts. /Greg

You are supposed to use ./autogen.sh, not ./configure. Calm down adn read my instructions again:
http://lists.xcf.berkeley.edu/lists/gimp-user/2009-July/015313.html

/ Martin

On 07/20/2009 09:35 PM, John Culleton wrote:

On Sunday 19 July 2009 05:13:06 am you wrote:

On 07/19/2009 03:16 AM, John Culleton wrote: > IMO

these required libraries should be embedded in the Gimp release itself but there may be turf issues that prevent that.

Embedding babl and GEGL in the GIMP tarball would make usage of GEGL by other projects much more complicated, and we don't want that. A library shared between many apps will have much more development and maintenance than a library only used by a single app, so we should encourage usage of these libraries by other projects.

/ Martin

I look at it from the point of view of the user, who just wants to install the program and get it running on his/her machine.

If you just want to install gimp and run it, use the package manager that comes with your distro. By nature, building software can be quite complicated and is not intended for "normal" users.

Also, please keep the discussion on-list.

/ Martin

On Monday 20 July 2009 03:41:14 pm Martin Nordholts wrote:

On 07/20/2009 09:35 PM, John Culleton wrote:

On Sunday 19 July 2009 05:13:06 am you wrote:

On 07/19/2009 03:16 AM, John Culleton wrote: > IMO

these required libraries should be embedded in the Gimp release itself but there may be turf issues that prevent that.

Embedding babl and GEGL in the GIMP tarball would make usage of GEGL by other projects much more complicated, and we don't want that. A library shared between many apps will have much more development and maintenance than a library only used by a single app, so we should encourage usage of these libraries by other projects.

/ Martin

I look at it from the point of view of the user, who just wants to install the program and get it running on his/her machine.

If you just want to install gimp and run it, use the package manager that comes with your distro. By nature, building software can be quite complicated and is not intended for "normal" users.

Also, please keep the discussion on-list.

/ Martin

For Slack users the packages are usually a year or more old so we get in the habit of compiling from a more current tarball. Also, many packages are not included in the distros. Open Cobol is a good example. Everybody compiles it. Currently I am at Gimp 2.6.6 and I had to go through the gegl and babl stuff again (new computer).

I see no compelling reason not to include the libs in the tarball.

On 07/20/2009 11:20 PM, John Culleton wrote:

I see no compelling reason not to include the libs in the tarball.

What is so problematic about fetching the libs from ftp.gimp.org?

If you suggest we should have the actual babl and GEGL code in the GIMP tarball, this is a bad idea. babl and GEGL are version controlled in different git repos, and it is not an option to version control them in the GIMP repo. They are separate, self-contained libraries.

/ Martin

On Monday 20 July 2009 05:25:12 pm Martin Nordholts wrote:

On 07/20/2009 11:20 PM, John Culleton wrote:

I see no compelling reason not to include the libs in the tarball.

What is so problematic about fetching the libs from ftp.gimp.org?

That is certainly an improvement over searching the web. But go to the top of this thread and see the turmoil one user went through trying to get Gimp going.

If you suggest we should have the actual babl and GEGL code in the GIMP tarball, this is a bad idea. babl and GEGL are version controlled in different git repos, and it is not an option to version control them in the GIMP repo. They are separate, self-contained libraries.

/ Martin

The version that matches the version of Gimp in the tarball is what should be included IMO. Presumably that is the version that is on gimp.org now. If e.g. Slackware can prepackage Gimp with all the required libraries it seems to me that the Gimp folks could do the same. But I guess we will have to disagree on this.

Regards,

On 07/20/2009 11:47 PM, John Culleton wrote:

The version that matches the version of Gimp in the tarball is what should be included IMO.

There is no version of GEGL that matches a given version of GIMP. GEGL is a library with an API (currently somewhat unstable due to immatureness of the library, but this is beside the point) that is independent of GIMP. Distributing GEGL in GIMP would imply that GEGL can not be bugfixed as maintainted separately, and this is wrong.

> If e.g. Slackware can prepackage Gimp with all the

required libraries it seems to me that the Gimp folks could do the same.

Nothing prevents you from stepping up and becoming part of the GIMP folks so to speak and do Slackware packaging.

/ Martin

On Mon, 20 Jul 2009 17:47:53 -0400, John Culleton wrote:

The version that matches the version of Gimp in the tarball is what should be included IMO.

Should GIMP then also include matching GTK+ and GLib? And other mandatory dependencies?

On Monday 20 July 2009 07:00:08 pm Jernej Simon?i? wrote:

On Mon, 20 Jul 2009 17:47:53 -0400, John Culleton wrote:

The version that matches the version of Gimp in the tarball is what should be included IMO.

Should GIMP then also include matching GTK+ and GLib? And other mandatory dependencies?

The hangup for many users is gegl and babl, and not the other requirements. The distros are more likely to include them. perhaps it is because gegl and babl are relatively new libraries, while the others have been with us for quite a while.

On Mon, 2009-07-20 at 21:09 -0400, John Culleton wrote:

On Monday 20 July 2009 07:00:08 pm Jernej Simon?i? wrote:

On Mon, 20 Jul 2009 17:47:53 -0400, John Culleton wrote:

The version that matches the version of Gimp in the tarball is what should be included IMO.

Ah, the old Windows way. Don't have it? We'll throw it in. It might break other apps, but hey, that's their problem. :)

Should GIMP then also include matching GTK+ and GLib? And other mandatory dependencies?

The hangup for many users is gegl and babl, and not the other requirements. The distros are more likely to include them. perhaps it is because gegl and babl are relatively new libraries, while the others have been with us for quite a while.

They could make mention of these on the Downloads Web page. I don't find any information on installing from source in the documentation, either.

Jon

On Mon, 2009-07-20 at 21:09 -0400, John Culleton wrote:

On Monday 20 July 2009 07:00:08 pm Jernej Simončič wrote:

On Mon, 20 Jul 2009 17:47:53 -0400, John Culleton wrote:

The version that matches the version of Gimp in the tarball is what should be included IMO.

Ah, the old Windows way. Don't have it? We'll throw it in. It might break other apps, but hey, that's their problem. :)

Should GIMP then also include matching GTK+ and GLib? And other mandatory dependencies?

The hangup for many users is gegl and babl, and not the other requirements. The distros are more likely to include them. perhaps it is because gegl and babl are relatively new libraries, while the others have been with us for quite a while.

They could make mention of these on the Downloads Web page. I don't find
any information on installing from source in the documentation, either.

From the INSTALL

The most important part is to make sure the requirements for a build are fulfilled. We depend on a number of tools and libraries which are listed below. For libraries this means you need to also have the header files installed.

****************************************************************** * Unless you are experienced with building software from source, * * you should not attempt to build all these libraries yourself! * * We suggest that you check if your distributor has development * * packages of them and use these instead. * ******************************************************************

It then goes on to list the necessary requirements which include gegl and babl.

Distros with any sort of reasonable package management can cope with all these things.

On Mon, 2009-07-20 at 21:09 -0400, John Culleton wrote:

On Monday 20 July 2009 07:00:08 pm Jernej Simon?i? wrote:

On Mon, 20 Jul 2009 17:47:53 -0400, John Culleton wrote:

The version that matches the version of Gimp in the tarball is what should be included IMO.

Should GIMP then also include matching GTK+ and GLib? And other mandatory dependencies?

The hangup for many users is gegl and babl, and not the other requirements. The distros are more likely to include them. perhaps it is because gegl and babl are relatively new libraries, while the others have been with us for quite a while.

Users don't build software from source. If you are building software yourself, then you are a developer. And you shouldn't really have a problem to compile these libraries then. If you have questions, you are of course free to ask them and we will try to help. But please don't ask us to simplify the build process in such awkward ways. The source tree is not aimed at users. Users should use whatever their distro offers.

Sven

On Tuesday 21 July 2009 04:59:45 pm Sven Neumann wrote:

On Mon, 2009-07-20 at 21:09 -0400, John Culleton wrote:

On Monday 20 July 2009 07:00:08 pm Jernej Simon?i? wrote:

On Mon, 20 Jul 2009 17:47:53 -0400, John Culleton wrote:

The version that matches the version of Gimp in the tarball is what should be included IMO.

Should GIMP then also include matching GTK+ and GLib? And other mandatory dependencies?

The hangup for many users is gegl and babl, and not the other requirements. The distros are more likely to include them. perhaps it is because gegl and babl are relatively new libraries, while the others have been with us for quite a while.

Users don't build software from source. If you are building software yourself, then you are a developer. And you shouldn't really have a problem to compile these libraries then. If you have questions, you are of course free to ask them and we will try to help. But please don't ask us to simplify the build process in such awkward ways. The source tree is not aimed at users. Users should use whatever their distro offers.

Sven

Understood. However I find Gimp 2.6 better than 2.4, which is what the latest stable version of my distro offers. So I will continue to be a user who compiles.

I must admit, compiling is becoming more difficult. Scribus uses cmake. Inkscape uses Automake and requires that you install Boehm-GC and Boost. The day of untar, ./configure, make and make install is apparently passing.

Von: John Culleton

I must admit, compiling is becoming more difficult. Scribus uses cmake. Inkscape uses Automake and requires that you install Boehm-GC and Boost. The day of untar, ./configure, make and make install is apparently passing.

Maybe you should switch to a distro that offers more current packages?

Michael