On 3/24/06, Martin Nordholts wrote:

The first step for me to be able to contribute to GIMP is making it build.

I have downloaded and compiled several libraries, but I am having problem with glib.

I downloaded the 2.10.1 glib tarball from gnome servers, and ran ./configure, make, make install succesfully (well at least it appeared that way). However, when I run the ./configure it fails when it checks glib version.

A couple of questions.

1. For which version of GIMP are you trying to compile these most modern libs? 2. Did you try to find prebuilt prerequisit RPMs for your distribution if they are missing from CD?

There should be a simpler way to get things done ;)

Alexandre

Hi Martin,

On Mar 23 at 11:14:57, Martin Nordholts wrote:

The strange thing is that when I run glib-config --version, it spits out 1.-something. That's weird isn't it?

What it's weird is that you got glib-config in glib-2.10.1. glib-config is only in old versions, recent versions use pkg-config files.

regards,

On Friday 24 March 2006 01:00, Martin Nordholts wrote:

Oops, forgot to tell.

I try to compile the latest tarball: GIMP 2.3.7.

Yep, I first and foremost looked for precompiled libs in Mandrivas packet manager, but I didn't find some of them, though lots of libs are directly installed from there.

Note that you can build the Source RPMs from Mandriva Cooker by building them with the "rpm --rebuild" command. You can find a list of mirrors here:

http://qa.mandriva.com/twiki/bin/view/Main/CookerMirrors

Regards,

Shlomi Fish

--------------------------------------------------------------------- Shlomi Fish shlomif@iglu.org.il Homepage: http://www.shlomifish.org/

95% of the programmers consider 95% of the code they did not write, in the bottom 5%.

Hi,

"Martin Nordholts" writes:

The first step for me to be able to contribute to GIMP is making it build.

I have downloaded and compiled several libraries, but I am having problem with glib.

I downloaded the 2.10.1 glib tarball from gnome servers, and ran ./configure, make, make install succesfully (well at least it appeared that way). However, when I run the ./configure it fails when it checks glib version.

The strange thing is that when I run glib-config --version, it spits out 1.-something. That's weird isn't it?

Not weird at all, see http://developer.gnome.org/doc/API/2.0/gtk/gtk-compiling.html

You probably also want to read the file INSTALL that comes with the GIMP source tree and should give you enough information to succeed building GIMP.

Sven

On 3/23/06, Martin Nordholts wrote:

Hello again!

The first step for me to be able to contribute to GIMP is making it build.

I have downloaded and compiled several libraries, but I am having problem with glib.

I downloaded the 2.10.1 glib tarball from gnome servers, and ran ./configure, make, make install succesfully (well at least it appeared that way). However, when I run the ./configure it fails when it checks glib version.

While I'm at it, why do you have to type ./configure? Isn't ./ just the name for the current directory?

Unlike dos/windows, linux doesn't search the current directory for programs to run unless . is in the path. Traditionally, . is not put in the path because of potential security problems, although some distros will put it as the last element in the path. (putting it before the last element can certainly be a problem.)

Does anyone know why it gimp/configure doesn't identify the fresh from-source-installation of glib 2.10.1?

If you did a ./configure with no arguments, "make install" installed glib into /usr/local, which isn't searched for by default by ./configure. You can tell pkg-config to look there by setting an environment variable. Off the top of my head, I think it is PKG_CONFIG_PATH, but you might want to type "man pkg-config" to make sure. So just run

PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure

instead of

./configure

and it should compile just fine. You'll have to do the same thing for every other ./configure you run that needs libraries installed in /usr/local.

(As an aside, the reason that the default location for installation is /usr/local/* instead of /usr/* is because the files installed in /usr/* are supposed to be managed by your package manager, while /usr/local is the traditional location for system-wide installation of programs that you've compiled yourself. If you want to run the development version of gimp alongside the stable version, you will need to install it someplace else. I personally use /usr/unstable.)

As Sven suggested, reading the INSTALL file should be helpful. I recommend you read all the UPPERCASE files, especially in gimp.

Rockwalrus