Re: Can't Build the GIMP

Hi Tor and all,

Thanks very much for your help.  Have made more progress.  Figured out that
I didn't need to copy pkg-config to gnome-config after all, as Tor mentioned
below.  Also, found the LIBTIFF, LIBJPEG, LIGPNG, LIBZ, and LIBICONV
environment variables, which allow me to point configure to the correct
locations for those libraries.  Now have yet another problem.  configure
quits after spitting out the following error message:

config.status: error: cannot find input file: plug-ins/perl/config.pl.in

Like it says, the subject file does not exist in Tor's gimp source
distribution which I downloaded.  How can I go about correcting this
problem?  BTW, I tried the --disable-perl option, and that didn't seem to
help.  configure still choked at the same point.

Thanks again.

s/KAM


----- Original Message -----
From: "Tor Lillqvist" <[email protected]>
To: <[email protected]>
Cc: "gimpwin users" <[email protected]>
Sent: Monday, October 21, 2002 4:06 PM
Subject: Re: [gimpwin-dev] Can't Build the GIMP


> Kevin Myers writes:
>  > I had to copy pkg-config.exe to gnome-config.exe (apparantly there is
still
>  > somewhere within the pkg-config 0.13 source code that it is refering to
>  > itself by the old gnome-config name),
>
> Nah, that shouldn't be necessary or useful (other than to shut up the
> silly misleading messages).
>
>  > Now the next problem seems to be that configure can't find libtiff.  My
>  > tiff-3.5.7-lib directory is at the same level as my gimp-1.2.4
directory.
>  > How do I tell configure where it should be looking to find libtiff?
>
> With the CPPFLAGS and LDFLAGS environment variables? As in:
>
> CC='gcc -mpentiumpro' CPPFLAGS='-I/where/ever/include -I...'
LDFLAGS='-L/where/ever/lib -L...'
./configure --disable-static --disable-perl --disable-print --prefix=/some/w
here ...
>
> --tml
>
>
>
>
> To Post a message, send it to:   [email protected]
> To Unsubscribe, send a blank message to:
[email protected]
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>