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

build issues

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.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.

a:2:{i:0;s:9:"(unknown)";i:1;s:0:"";} Dov Kruger 06 Oct 22:54
  build issues Carol Spears 07 Oct 02:38
Dov Kruger
2004-10-06 22:54:22 UTC (over 19 years ago)

a:2:{i:0;s:9:"(unknown)";i:1;s:0:"";}

Hello,

Trying to build gimp again, we have a problem on RedHat EE 3. gimp-2.0.4 requires gimp-print; most other packages are already installed under redhat.

Each package is configured using:

./configure --prefix=/opt

building gimp-print-4.2.6 or 5.0.0-beta, we get the error:

Making all in foomatic make[3]: Entering directory `/root/gimp-print-4.2.6/src/foomatic' rm -r foomatic-db
rm: cannot lstat `foomatic-db': No such file or directory make[3]: [foomatic-stamp] Error 1 (ignored) ./foomatic-generator -m ./foomatic-printermap -t ./foomatic-templates -d noijs -o
Loading options from ./printer_options...done. Loading options from ./stp_limits...done. Loading options from ./printers...done. Loading printer ID translation table from ./oldprinterids...done. No foomatic printer IDs for gimp-print printer escp2-pm4000px. No foomatic printer IDs for gimp-print printer pcl-850.

... etc...

Evidently gimp-print cannot complete without the foomatic stuff. I built foomatic in /opt, it appears to buld correctly but the gimp-print package seems to use its own foomatic inside (and I had no idea what foomatic is really doing anyway)

Thanks for your help. Dov

ps.
My suggestion to avoid repeated requests like this: Have a single package with all the gimp dependencies in it. Who cares if there are extra versions of gtk, gimp-print, etc lying around. Since you don't provide rpms for many systems, why make people without supported binaries go through hand building all the dependencies, with all the attendant problems? It's much easier in the long run to just support a single version for each release in one big happy build that all works together.

Carol Spears
2004-10-07 02:38:21 UTC (over 19 years ago)

build issues

On Wed, Oct 06, 2004 at 04:54:22PM -0400, Dov Kruger wrote:

Hello,

Trying to build gimp again, we have a problem on RedHat EE 3. gimp-2.0.4 requires gimp-print; most other packages are already installed under redhat.

Each package is configured using:

./configure --prefix=/opt

./configure --help
gives you everything you need to know. to fix this problem try: ./configure --prefix=/opt --disable-print

i think gimp builds have been like this since gimp-1.2. gimp-print and gimp are two separate projects; i dont know if this is the reason for the circular dependency. easily handled in the configuration though.

carol