Thanks for the advice Iohannes. I think I will give the CVS version of GEM a shot. I have not yet used a CVS, but I would imagine everything I need to know is documented clearly enough to make that process relatively straightfoward.
Then I suppose I will go to rpmfinder.net, and download libjpeg-devel, libtiff-devel, libftgl-devel, freetype2-devel and ImageMagick++-devel. If any of those libraries are installed in my OS, then I think that the OS will notify me, and I can skip installation for those libraries.
As I install, I will make sure to pay attention to the config.h file, so I can know where GEM is looking for its libraries.
I will report back to you with exactly what libraries I end up using in the install process.
cheers,
David K.
it doesn't need to be somewhere near pd (though m_pd.h should be in an accesible path, like /usr/local/include or the like)
what i meant in the docs is: if GemLibs are here: /path/to/wherever/GemLibs/ then Gem's config.h-file should be here: /path/to/wherever/Gem/src/Base/config.h (or, alternatively, if the gem-sources come with version-number) /path/to/wherever/gem-0.90/src/Base/config.h
anyhow, it might well be that the GemLibs are not needed altogether on your distribution (i'm no specialist with fedora)
provided by GemLibs are following libraries: libjpeg libtiff GLTT + freetype but all of them are most probably outdated
if it is an option for you, i would try to install (at least) the following development-packages from your distribution (probably the names are not 100% correct) libjpeg-devel libtiff-devel libftgl-devel + freetype2-devel
hint: try to not use GLTT, but rather FTGL!
hint: if you are using the CVS-version of Gem (i'd recommend this), you can additionally use ImageMagick++-devel AND all of the image-libraries (jpeg, tiff, imagemagick) are _optional_ (this is: Gem will still compile and run (with limited functionality though) if you don't have any or one of this libraries)
please report back which packages did work for you.
mfg.asd.r IOhannes