![[Way qool image]](http://www.rru.com/Images/blackhole3.gif)
Just the FAQs, please!
Last updated: Thursday, 10-Sep-1998 01:07:23 CDT
| General | Plug-Ins | Script-Fu | Fonts | File Formats | Using | Platforms |
|---|
If your question isn't here, it might be more of a Developer FAQ than a user FAQ. Look there before you panic.
The latest version of this FAQ should always be available at http://www.rru.com/~meo/gimp /faq-dev.html .
You may submit material to the maintainer, Miles O'Neal, at meo@rru.com . [an error occurred while processing this directive]
The ``GNU Image Manipulation Program'' sired by Spencer Kimball & Peter Mattis.
In their own words, ``The GIMP is our answer to the current lack of free (or at least reasonably priced) image manipulation software for Linux and UNIX in general.''
Note: Originally, GIMP stood for ``General Image Manipulation Program''. The change to GNU is fairly recent.
The best bet is to check out the GIMP home page which includes pointers to the latest source, as well as complete binaries for a variety of platforms, including at least Linux (a.out and ELF), FreeBSD-2.1, HP-UX, SunOS and Solaris 2.4, and SGI. More may be available by now; go check the web page. Go on! Vamoose! You can come back here after you get it!
Version 1.0.0 is out, and very stable. Get the production version, and get rid of all your old developer versions!
Yes. It is available at http://manual.gimp.org/ in HTML form, and ftp://manual.gimp.org/pub/manual/ n Frame, HTML, PDF and PS formats.
A Windoze version was announced on April Fool's Day, and those who missed the opportunity to download it should be sad, indeed; the announcement itself (a work of art!) follows (the URLs are no longer active):
I got a little restless during spring break, so, besides sleeping a lot, and scaring squirrels in the yard, I did mad run of hacking and managed to create a suprising beast: GIMP on Win32. http://www.gimp.org/gimp-win32.gif Yep, it really wasn't too hard, considering the way GTK abstracts out the underlying GUI. It clearly needs work though, but it's for the most part fully functional. Just crashes a lot. But you guys can take a look at it: ftp://ftp.gimp.org/pub/gimp/win32/ -Yosh
These are similar to the layers found in tools such as Adobe's PhotoShop[tm]. Think of a stack of slides or filters, such that looking through them you see a sort of composite of their effects. For more information, check out the S&P introduction to layers.
Probably the prime GIMP resource page is maintained by Quartic at http://www.nuclecu.unam.mx/~federico/gimp/el-the-gimp.html .
A list of GIMP tutorials is available at http://abattoir.cc.ndsu.nodak.edu/~nem/gimp/tuts from Nem W Schlecht.
The GIMP Documentation Project, spear-headed by Michael J. Hammel, is the central documentation point for users.
Send email to majordomo@scam.xcf.berkeley.edu with the following command in the body (subject line is irrelevant):
subscribe gimp-user your-email-addresssubstituting your preferred email address for the string ``your-email-address'' .
None of the newer versions (since 0.60) need Motif. S&P developed their own, very slick toolkit called gtk, for the GIMP.
Probably because it can't find them. 8^)
There are a couple of solutions. The best one, if you have superuser access on your system, or a cooperative system administrator, is to add the GIMP's library directory to the system library configuration. To do this, edit /etc/ld.so.conf to include /usr/local/lib and then type
ldconfig
and things should work from then on.
If you can't do this, add the directory to your LD_LIBRARY_PATH environment variable. Be sure you do this in your shell's startup scripts as well.
If you have old versions of the libraries, you will probably need to remove them first, especially if they are in standard system locations such as /usr/lib . Don't just delete them, though; move them somewhere safe, install the new ones, and try again. Then make sure everything else still works; you may have other programs on your system which require the old versions. The ideal response in such a case is to rebuild all the programs to use the new libraries. Where this isn't possible, you will just have to experiment with trying them in different locations, or statically linking them to one or more programs.
Yes. You can run xscanimage, the front end to SANE (Scanner Access Now Easy) either as a GIMP extension or in stand-alone mode. This supports Mustek and HP flatbed scanners, as well as the Connectix color QuickCam camera.
Yes. In either the system-wide gimprc file or your personal gimprc file, uncomment the line that includes ``install-colormap''.
If the GIMP gives you a message similar to either of these when you try to start it:
Xlib: extension "MIT-SHM" missing on display "198.51.29.58:0.0".
or
** WARNING **: XShmAttach failed!
then you need to run it with the --no-xshm option.
This happens for one of two reasons. Either your X display server does not have the shared memory option, or you are running the gimp on a different system than the one on which it is displaying. In the former case, you may wish to look into different X servers, because shared memory can give you MUCH better performance. In the latter case, you will just have to live with it, since different systems can't generally share the same memory space.
For a while, these were provided separately in the developer versions. For some time now a very good, "minimum" set of these has been shipping with the GIMP. More are available as "extra" data bundles from any of the download sites.
Others are available from various places. Adrian "Numerical Excess" Likins has a page with lots of gradients and palettes at http://www4.ncsu.edu/~aklikins/gimp/AG.html .
This error message should say something like "the plug-in (or the main GIMP app) I was talking to has exited before returning any results, so I assume that it has crashed."
Somewhere around 0.99.16 or 0.99.17 , configure stopped searching /usr/local for include files and libraries, at least for some of the common packages. Also, on some platforms (FreeBSd, for instance), things may get installed under /usr/X11R6/share instead of /usr/local . Running autoconf and automake might solve this, but for the rest of us, just set the following variables before running configure (substituting as neceesary for /usr/local ):
csh, tcsh, etc:
setenv CFLAGS -I/usr/local/include
setenv LDFLAGS -L/usr/local/lib
sh, ksh, bash, etc:
CFLAGS=-I/usr/local/include ; export CFLAGS
LDFLAGS=-L/usr/local/lib ; export LDFLAGS
On Solaris, you may need to set LDFLAGS to
"-L/usr/local/lib -R/usr/local/lib" .
The instructions state that these directories will be searched automatically, but in at least some cases, this is not correct.
Yes, you have to have some form of X server - the GIMP is an X application! However, if you wish to run in batch mode, you can run with a special, frame-buffer-less X server called Xvfb, which doesn't require a graphics card or mess with your screen:
Xvfb :1 -screen 0 10x10x8 -pixdepths 1 &
gimp --display :1.0 --no-interface --batch "commands" ... &
The first command starts the special X server; the second is an
example of how to invoke the GIMP in batch mode. When you are done
using the GIMP this way for a while, kill off Xvfb so it doesn't
waste system resources. If you expect to use gimp this way a lot,
you might want to leave Xvfb running for better response time.
http://www.cs.utexas.edu/users/mschaef/gimpicons/index.html
Like most graphics applications: the GIMP is resource intensive, which means it directly benefits from more memory, higher end graphics cards, and faster disks. Its the nature of the beast (computer graphics) and not necessarily a problem with the GIMP (although there are probably areas it could use performance work - what program couldn't?).
The easiest speedup is to invoke the GIMP with the "--no-data" option. This prevents the GIMP from loading patterns, brushes, and similar resources when it starts. You may benefit slightly from the "--no-splash" option as well; you mihght want to time that one to see if it really helps enough to be worthwhile.
Plug-ins are external modules that actually do the nifty graphics transformations. There is a plug-in registry with the latest plug-ins, maintained by Ingo Lütkebohle. [Special thanks to Adam Moss for the original registry!]
First, copy the plug-in[s] to your plug-in directory (typically /usr/local/lib/gimp/$VERSION/plug-ins/).
If you are running 0.54 or earlier, you will need to add the plug-in to the system gimprc or your .gimprc file. Look in the file for a plug-in with related functionality (blur, plasma, or whatever), copy that line, and change the new line appropriately. Be sure to use unique accelerators!
As of version 0.60, it is much simpler. After copying the plug-in to its proper directory, just run the GIMP. It should automatically find new plug-ins.
You'll need a copy of the source directories. Build the GIMP. Place the new plug-in in the plug-ins directory. The docs with the new plug-in hopefully identify any special libraries it needs. Look for a plug-in with similar libraries (if all else fails, look at xpm and whirlpinch).
With newer versions, if the plug-in is contained in a single source file, you should just have to run the gimptool in the plug-in's directory :
gimptool --build plugin.c
For older versions, there are several methods. The first two walk you through a number of steps manually; these are the most thorough, but also require more work on your part. The last ones are scripts of one sort or another, and are easier on your part -- if they work with your system. Go ahead and try - you can always fall back on the first methods.
make
and it should build. Install it wherever your other plug-ins
are installed.
whirlpinch
whirlpinch.c
whirlpinch.o
In this case, you would remove the first and last files, leaving
the whirlpinch.c file. Now type
make
to rebuild the old plug-in.
Copy the output (cut and paste it!) into a file. Edit the file and change all occurances of "whirlpinch" (or whatever) to the name of the new plug-in. Execute the file you just edited. For instance, if the file is make_plug-in, just type
make_plugin
and it should work. The copy the plug-in to wherever the others
are installed on your system.
First, load Makefile-pi provided by
Ciccio C. Simon .
Change all occurances of the word sharpen in
Makefile-pi to the name of the new plug-in. Then type
make -f Makefile-pi
and watch it (hopefully) work.
If it doesn't work, try the next method.
First, load the compile-pi script provided by Jeremy Dinsel . Change the permissions on compile-pi as follows:
chmod ugo+rx compile-pi
and type
compile-pi help
for instructions. Follow those instructionms. If this one
also fails, go back to the earlier, manual methods; you
have too picky a configuration for the simple methods to
work.
If you need more help, ask your system administrator or a handy programmer, or get a good book on make (such as O'Reilly's). You may want to join the GIMP developer's list as well (see the Developer FAQ).
The plug-in registry referenced above is the place to check.
Some of the plug-ins have proven unstable. These have been moved into a separate download, which should be available wherever you got the GIMP, in the file gimp-plugins-unstable-VERSION.tar.gz or gimp-plugins-unstable-VERSION.tar.bz2 .
Since this list may change frequently, the unstable plug-ins are no longer listed here.
Normally it means that the script is trying to use a particular font that isn't available on your system - it's either not installed or not in your X server's FONTPATH. The base script-fu package makes extensive use of the freefont package, and at least one font (AlfredDrake) from the sharefont package.
Net-fu is a web-based interface to a script-fu server. The work is done at a remote site. To see Net-fu, point your web browser at http://scheme.XCF.Berkeley.EDU/net-fu/ or http://www.cooltext.com/ . Any web browser can read this page; the browser must be Java-enabled to actually run Script-fu.
The freefonts and sharefonts packages are both available from ftp://ftp.funet.fi/pub/Linux/sunsite/X11/fonts/ or other Sunsite mirrors. If you get the sharefonts package, be sure and read the various licensing agreements, and abide by them.
You need to copy the gtkrc file that comes with the GIMP source (in the top level directory) into $HOME/.gimp/gtkrc . As of 0.99.10, this should be recognized. You then go in and edit the default font style, the one that looks like this:
style "default"
{
font = "-adobe-helvetica-medium-r-normal--*-100-*-*-*-*-*-*"
}
I'm sure ther's a lot of clever stuff that can be done
here, and I'll try to track it down soon, but in the meantime,
just change that "100" to something larger, like "120" or "140".
(The number is points * 10, so 100 is a 10 point font).
Obviously, you could stick in any font you have available.
These are 16 bit fonts, with thouousands and thouousands of characters. And the characters are more complex, which means (usually) more bits per character, which means more memory and more processing time.
This includes fonts such as kana, kanji, song ti, mincho and gothic. (If you look carefully at the fully qualified font name for gothic via xfontsel, you'll see clues. It's a daewoo font. The gothic name is misleading to western minds, but no doubt means something to its author[s].)
Check one of these out in a program that shows a font as pages (such as xfd).. You can keep hitting next page to see a new page of characters, almost forever.
If neither your X server nor your X font server supports you
can try one of the TruType font servers:
xfstt (http://sunsite.unc.edu/pub/Linux/X11/fonts/)
or
xfsft (http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/ .
xfstt supposedly has limitations on the font size.
XCF is the GIMP's "native" format. This will preserve all information about an image, including the layers.
All the common formats, and many more as well, including GIF, TIFF, JPEG, XBM, XPM, PostScript, and BMP. Plug-ins are used to load and save files so adding new file types is very simple, compared to other graphics programs.
As of Jul 1, 1998, the list of supported types included BMP, CEL, FITS, FLI, GBR, Gicon, GIF, GIcon, HRZ, JPEG, PAT, PCX, PIX, PNG, PNM, PostScript, SGI, Sun Raster, TGA, TIFF, XPM, XWD and XCF. Bzipped, Gzipped and Xdelta'd files are understood, and URL support is provided.
Of course, plug-ins for other types may be available at the plug-in registry .
The two most likely problems are related to image type and layers. For instance, your image type must be "Indexed" for GIF, but "RGB" for TIFF. Try a different image type (look under the "Image" menu). If you have more than 1 layer in your image, you probably need to merge the visible layers, and/or "flatten" the image. Both operations are available under the "Layers" menu or from the "Layers" dialog. Flattening will destroy any background transparency.
Yes; the GIMP has a file format just for this - the XCF format. Don't flatten the image or merge the layers as you would to save to other formats! This will only work with the XCF type.
Create a new image large enough to hold the selection. Copy the selection, then paste it into the new image. Crop the new image. Flatten, etc, as necessary. Now save it.
The script-fu-selection-to image can also be used to cut a selection out of an image and create a new image with it.
Before saving the image, select "Layers->Flatten Image". It would be more intuitive if it was called something like "Remove Alpha"...but that's generally not its primary function. It just happens to remove alpha.
Open the additional image via the File->Open
menu. Then Select->Select all. Edit->Copy.
Move the cursor to the edited image. Edit->Paste.
This drops the new image (selection) into the
middle of the edited image. Move it around as
necessary, then anchor it.
In general, small fonts won't ever look quite as nice as large ones. But there are a couple of things to try.
Go to the menu selection you are interested in. Keeping it selected (hold the mouse's menu selection down if necessary), press the key sequence you wish to assign to the menu. It will appear on the right of the menu. The new binding will be saved and used in future GIMP sessions.
The equivalent method in .99, 1.0 or later would be to have two layers, and create an alpha mask (add layer mask from the layer ops menu) and insert the "mask" layer into it.
Not at this time. It's in the works for a future release.
This is one of the few platforms where gcc isn't the right answer. Acording to Stephen Eglen,
During compilation, cc doesn't like the following code found in
app/layer.c (line 56) and app/channel.c (line 45).
enum {
LAST_SIGNAL
};
static gint layer_signals[LAST_SIGNAL] = { 0 };
The compiler comes up with the following error:
cc: Error: layer.c, line 56: In the declaration of "layer_signals",
the array bound "LAST_SIGNAL" is not a positive integer.
static gint layer_signals[LAST_SIGNAL] = { 0 };
So I changed the line to: vv
static gint layer_signals[LAST_SIGNAL+1] = { 0 };
^^
which kept the compiler happy, although maybe now that has broken
something else.
I also had to use a private colourmap by adding the following to gimprc:
(install-colormap)
Without this private colourmap, I still get a sigabrt:
** ERROR **: BadMatch (invalid parameter attributes)
gimp fatal error: sigabrt caught
[Note also that once I got it working with cc, I didn't recompile it
under gcc to see if gcc works with private colourmaps.]
ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz
If you are using a 64-bit OS, you need to add the `-o32' option for the compiler, or use gcc. With the SGI compiler, you may also need to play with optimization. Some modules may have exhibit problems unless compiled with `-O1' or even `-O0'.
Script-Fu requires the POSIX-compliant regex functions, which SGI only supports with IRIX 6.2 and later versions. The GNU version of regex should work just fine, though, and is available at:
http://wuarchive.wustl.edu/systems/gnu/regex-0.12.tar.gz
Quartic posted this fix, which showed up as a result of a GIMP IRC discussion:
(This is Steve, aka valiant@deeptht.armory.com.)Here's the fix for the configure/SCO/-lXext problem:
In gtk+/configure.in, line 75:
The last argument should be: -lX11 $X_EXTRA_LIBS
Instead of: -lX11
Run autoconf and configure again.
The reason this broke: OSR5 requires -lsocket for the X stuff to work. This is detected correctly a few steps prior. In the -lXext test however, a compilation is attempted with XShmAttach() to see if it is resolved properly with -lXext. Since in this test -lsocket is not included, link errors are produced and the test fails, so configure assumes -lXext does not help and does not put it in the Makefiles.
The GIMP is interacting in such a way with your system that it thinks you have XIM extensions when you don't. Run the configure script again, with the `--disable-xim' option, and recompile.
You can also try compiling with `--disable-shared'.
Or you can install a version of X11R6. 8^)
If you are linking with GNU's ld, this is probably the problem.
Try using /usr/ccs/bin/ld instead.
If you just want to use freefonts or sharefonts, you can copy these files into the appropriate directory (such as /usr/openwin/lib/fonts/freefonts/ or /usr/openwin/lib/fonts/sharefonts/), or merge them with the appropriate fonts.dir and fonts.scale files if you mixed in freefonts and sharefonts with existing fonts:
Or just try using fontadmin instead of
mkfontdir .
I've never run into a Solaris system missing this, but according to From Neil Corlett:
The 'fontadmin' tool is a openwin demo program and sometimes does not exist. To properly add fonts the finagled directory requires fonts.dir, fonts.scale files to exist. mkfontdir does the first of these OK. For the second I built groff and downloaded type1inst-0.6.1 from an X contrib archive. type1inst (which needs groff) will build the fonts.scale file from the pfb files automatically.Solaris 2.6 is supposed to include better font editor and admin tools.
There may be a number of reasons. Several peoples' answers are here. The most detailed answers, list first, are the best bets with their noted versions.
According to resident Gimp on SOlaris guru Jim Harmon, more recent versions (0.99.25 on) should compile easily, but you may need to make a change in /usr/graphics/gtk-config.in:
OLD:
--libs)
echo -L${exec_prefix}/lib -L/usr/openwin/lib -R/usr/openwin/lib \
-lgtk -lgdk -lglib -lXext -lX11 -lsocket -lnsl -lm
;;
NEW: (subs. your own GTK path for /usr/graphics )
--libs)
echo -L${exec_prefix}/lib -L/usr/openwin/lib -R/usr/openwin/lib \
-L/usr/graphics/gtk+-0.99.10/gtk/.libs \
-R/usr/graphics/gtk+-0.99.10/gtk/.libs -lgtk \
-L/usr/graphics/gtk+-0.99.10/gdk/.libs \
-R/usr/graphics/gtk+-0.99.10/gdk/.libs -lgdk \
-L/usr/graphics/gtk+-0.99.10/glib/.libs \
-R/usr/graphics/gtk+-0.99.10/glib/.libs -lglib \
-lXext -lX11 -lsocket -lnsl -lm
;;
Jim Harmon compiled GIMP 0.99.19 and GTK+ 0.99.5 on Solaris 2.5, SPARC 5. Here are the steps he took:
(*) If you're installing a NEW VERSION, first: (*) o cd(/usr/graphics/gtk+ ) (*) o make uninstall clean (*) o rm -r ~/.gimp THEN: o mkdir /usr/graphics o mv g*.tar.gz /usr/graphics o tar xvfz gtk+-0.99.5.tar.gz created /usr/graphics/gtk+-0.99.5 o cd gtk+-0.99.5 o ./configure, make, make install (executed successfully) o cd .. o tar xvfz gimp+-0.99.19.tar.gz created /usr/graphics/gimp+-0.99.19 o cd gimp+-0.99.18 o ./configure NOW: *** Edit "config.status" *** o vi config.status /LDFLAGS o change: (note, the following are SINGLE LINES, remove any "\" characters and duplicate objects in the string if you cut/paste these into your config.status file...) s%@LDFLAGS@% -L/usr/openwin/lib -R/usr/openwin/lib \ -lgtk -lgdk -lglib \ -lXext -lX11 -lsocket -lnsl -lm%g to: (*) s%@LDFLAGS@% -L/usr/local/lib -R/usr/local/lib \ -L/usr/openwin/lib -R/usr/openwin/lib \ -L/usr/graphics/gtk+-0.99.5/gtk/.libs \ -R/usr/graphics/gtk+-0.99.5/gtk/.libs -lgtk \ -L/usr/graphics/gtk+-0.99.5/gdk/.libs \ -R/usr/graphics/gtk+-0.99.5/gdk/.libs -lgdk \ -L/usr/graphics/gtk+-0.99.5/glib/.libs \ -R/usr/graphics/gtk+-0.99.5/glib/.libs -lglib \ -lXext -lX11 -lsocket -lnsl -lm%g (*) O To SAVE SPACE in compiling, in the config.status file, REMOVE the "-g" option from the CFLAGS line: [was] s%@CFLAGS@% -g -I/usr/openwin/include -O2 -Wall%g [is] s%@CFLAGS@% -I/usr/openwin/include -O2 -Wall%g o ./config.status, make, make install (In other words, where "-lgtk -lgdk -lglib" appear on the LDFLAGS line, add the GTK+ path to the libs with the format of "-L/usr/graphics/gtk+-0.99.3//.libs -R/usr/graphics/gtk+-0.99.3//.libs -l", subsituting gtk/gdk/glib for ) (*) Also bear in mind that "/usr/local/lib" won't exist if not added as shown to LDFLAGS. - - - CAVEATS: I'm using the precompiled GCC 2.7.2.3 for Solaris 2.6, and gmake instead of make. To get GCC and GMAKE working, I had to set the paths to /usr/xpg4/bin and /usr/ccs/bin to the PATH variable, so that different compiler tools could be found. (ar, bison, cpp, etc.)
Jim Harmon compiled GIMP 0.99.18 and GTK+ 0.99.3 on Solaris 2.5, SPARC 5. Here are the steps he took:
o mkdir /usr/graphics
o mv g*.tar.gz /usr/graphics
o tar xvfz gtk+-0.99.3.tar.gz
created /usr/graphics/gtk+-0.99.3
o cd gtk+-0.99.3
o ./configure, make, make install
(executed successfully)
o cd ..
o tar xvfz gimp+-0.99.18.tar.gz
created /usr/graphics/gimp+-0.99.18
o cd gimp+-0.99.18
o ./configure
NOW: *** Edit "config.status" ***
o vi config.status
/LDFLAGS
o change:
(note, the following are SINGLE LINES, remove any
characters in the string if you cut/paste it into your
config.status file...)
s%@LDFLAGS@% -L/usr/openwin/lib -R/usr/openwin/lib -lgtk -lgdk -lglib
-lXext -lX11 -lsocket -lnsl -lm%g
to:
s%@LDFLAGS@% -L/usr/openwin/lib -R/usr/openwin/lib
-L/usr/graphics/gtk+-0.99.3/gtk/.libs
-R/usr/graphics/gtk+-0.99.3/gtk/.libs -lgtk
-L/usr/graphics/gtk+-0.99.3/gdk/.libs
-R/usr/graphics/gtk+-0.99.3/gdk/.libs -lgdk
-L/usr/graphics/gtk+-0.99.3/glib/.libs
-R/usr/graphics/gtk+-0.99.3/glib/.libs -lglib -lXext -lX11 -lsocket
-lnsl -lm%g
o ./config.status, make, make install
(In other words, where "-lgtk -lgdk -lglib" appear
on the LDFLAGS line, add the GTK+ path to the libs
with the format of "-L/usr/graphics/gtk+-0.99.3//.libs
-R/usr/graphics/gtk+-0.99.3//.libs -l", subsituting
gtk/gdk/glib for )
--------------------------------
CAVEATS:
I'm using the precompiled GCC 2.7.2.3 for Solaris 2.6,
and gmake instead of make. To get GCC and GMAKE working,
I had to set the paths to /usr/xpg4/bin and /usr/ccs/bin
to the PATH variable, so that different compiler tools
could be found. (ar, bison, cpp, etc.)
According to Keyyly Price, here's a major one for 0.99.10 .
``If you do a -lX11, you must also include -lsocket, or it won't compile
anything of X on Solaris 2.5. X doesn't have the socket lib.
Which means you'll need to setenv LIBS -lsocket while running configure if
you run Solaris 2.5.''
Will Lowe did the following to get the GIMP compiled for Solaris 2.5.1 : (You should replace /usa/lowe/usb_lowe/gimp in each "-L" part with whereever you are compiling gimp, and replace /usa/lowe/gimp/lib in the "-R" parts with whereever you're going to install gimp. -Will)
Get gimp source (duh) (gimp-0.99.9).
uncompress and untar the source.
./configure --without-libtiff
rm docs/pdb.info
gimp/gtk+/gdk/gdkimage.c
Remove these three lines:
#if defined (HAVE_IPC_H) && defined (HAVE_SHM_H) && defined (HAVE_XSHM_H)
#define USE_SHM
#endif
gimp/gtk+/gdk/Makefile:
change the variable "libgdk_la_LDFLAGs" to include:
-L/usa/lowe/usb_lowe/gimp/gtk+/glib/.libs -R/usa/lowe/gimp/lib
before "-lglib"
gimp/gtk+/gtk/Makefile:
change the variable "libgtk_la_LDFLAGS" to include:
-L/usa/lowe/usb_lowe/gimp/gtk+/gdk/.libs -R/usa/lowe/gimp/lib
before "-lgdk"
gimp/libgimp/Makefile:
change the variable "libgimp_la_LDFLAGS" to include:
-L/usa/lowe/usb_lowe/gimp/gtk+/glib/.libs -R/usa/lowe/gimp/lib
before "-lglib"
change "libgimpui_la_LDFLAGS" to include
-L/usa/lowe/usb_lowe/gimp/gtk+/gtk/.libs -R/usa/lowe/gimp/lib
before "-lgtk"
gimp/plug-ins/dgimp/dgimp.c
move "#include <sys/types.h>" to above "#include <sys/socket.h>"
gimp/plug-ins/dgimp/lpg.c
same as dgimp.c
For 0.99.pre11, Sheldon E. Newhouse suggests the following
change to the libtool files:
#archive_cmds='$LD -G -z text -h $soname -o $lib$libobjs$deplibs' archive_cmds='$LD -G -h $soname -o $lib$libobjs$deplibs'Or, you can just grab the current binaries from http://www.cs.wustl.edu/~paul/ , courtesy of T. Paul McCartney.
A bug appeared in the code. Here's the pacth, courtesy of Petr A. Ovchenkov and Dov Grobgeld:
-------------- cut here --------------
*** plug_in.c.orig Sun Oct 12 18:49:27 1997
--- plug_in.c Sun Oct 12 18:39:25 1997
***************
*** 219,226 ****
g_warning ("shmat failed...disabling shared memory tile transport\n");
shm_ID = -1;
}
! else
! shmctl (shm_ID, IPC_RMID, 0);
}
}
--- 219,226 ----
g_warning ("shmat failed...disabling shared memory tile transport\n");
shm_ID = -1;
}
! /* else
! shmctl (shm_ID, IPC_RMID, 0); */
}
}
***************
*** 336,341 ****
--- 336,345 ----
plug_in_destroy (plug_in);
}
+ if ( shm_ID != -1 ) {
+ shmctl( shm_ID, IPC_RMID, 0 );
+ shm_ID = -1;
+ }
}
void
-------------- cut here --------------
Yes. Try the following:
ftp://s9412a.steinan.ntnu.no/pub/gimp/
http://www.linkexplorer.com/gimp
According to Rob Payne...
There are old .src.rpm's on ftp.redhat.com for gimp and gtk that if used to build new gtk+ and gimp will create all kinds of headaches for the builder.
The gtk SPEC file manually moves header files from gtk default installation place, and then the CFLAGS returned by gtk-config are incorrect when it comes time to build/install gimp. I was successful in bringing the gtk+ SPEC file up to date by removing the following lines from (gtk-970925.spec) to build 0.99.7 and 0.99.8:
(cd $RPM_BUILD_ROOT/usr/local/include
mkdir glib
mv glib.h glibconfig.h glib)
Of course, the %files section of that SPEC need to be changed, as well to
include the differences in places for the header files, and to include
gtk-config.
I hope that information is useful to someone. If you have any questions about any of this, please let me know.
Another possibility is for this error (far less common) is that there is an old library compiled with the other hanging around somewhere on the system. Remove old copies of libgimp.
You probably just installed the graphics libraries. You also need to install the development portion as well; it's called the libgr source package. After installing that, GIMP should compile easily.
``Some of the X include files and libraries are not in /usr/include/X11 and /usr/lib/X11 as you may expect. This is because HP allows support for X11R4 and X11R5 on the same machine. You must modify a configuration file so that the Makefile created by imake looks for these files and libraries in an alternate location. See "Motif and Xt" on page A-5 and "Xaw and Xmu" on page A-6 for details on installation of OSF/Motif, Xt, Xaw and Xmu.
...
``HP does not ship or support these widget libraries; however, they are widely used for X public domain software. Binaries and header files are available from the Interworks library. Source is available from public domain archives. The name of the binary package in the Interworks library is x8.0s700.tar.Z. You may also be able to locate these files on another machine and copy them to your machine.''
The ref'd package is at:
ftp://www.interworks.org/pub/comp.hp/
Look for the x8.0s[378]00.tar.Z files.
You are probably not using the GNU make. Most, if not all, non-GNU makes will fail on the GIMP makefiles. Get the GNU make package.
It's a bug in AcceleratedX with shared memory. Turn off shared memory when you start the GIMP (--no-xshm) or pick up the patch to AcceleratedX's X server from ftp://ftp.xinside.com/ax/patches/v3.1/beta/ . At least one person has found this bug (or another one with the same symptoms) to still be present in 4.1 .
This is a bug in XFree. You need to upgrade to XFree3.3.2 .
Here is a patch from Jim Geuther. This will disappear from the FAQ when it's fixed in the master source copy.
Contributors: Spencer Kimball & Peter Mattis, Thomas Bahls, Zach Beane, Brandon Beattie, Seth Burgess, Mats H. Carlberg, Neil Corlett, Christopher Curtis, Jeremy Dinsel, Ian Donaldson, Bert Driehuis, Pat Dunn (?), Stephen Eglen, Eugene Filippov, Rial Fletcher, Trond Eivind Glomsrĝd, Michael J. Hammel, Pete Harlan, Jim Harmon, Thimo Jansen, Christoph Kukulies, Philippe Lavoie, Marc Lehmann, Adrian Karstan Likins, Will Lowe, Ingo Lütkebohle, T. Paul McCartney, Wenxin Mao, Adam Moss, Sven Neumann, Sheldon E. Newhouse, Miles O'Neal, Rob Payne, piranha (alix albert), Kelly Price, Quartic (Federico Mena), Raphael Quinet, Deon Ramsey, Donovan Rebbechi William L. Sebok, Terrelle Shaw, Ciccio C. Simon, Yosh (Manish Singh), Mike Sweet, Owen Taylor, Mike Terry, Tyzen
Last updated: 10 September 1998 [an error occurred while processing this directive]