On Wednesday, 03 June 1998, at 22:49:31 (-0500),
Michael Jinks <[EMAIL PROTECTED]> wrote:

> I have version 1.4-10 according to rpm.  The tarball on Rasterman's ftp site is
> labeled 1.4 (no -10) and the source files I have are dated, uh. . . May 8.

I personally don't touch RPM's.  If I can't make it work from tarballs, I
don't use it.  (Of course, I can make E/Imlib work from tarballs, so....) :)

> How do I check this?  The only thing I can think of to check is config.h, and
> it's a little confusing.  For example:

Check the link line for "-ltiff", "-lpng", etc.

> /* Define if you have the tiff library (-ltiff).  */
> /* #undef HAVE_LIBTIFF */
> 
> I take this to mean that if we fail to find the tiff library, we would uncomment
> this line, but since it's present we do nothing.  Right?  I'm basing this
> partially on the fact that there are also lines that look like this one:
> 
> /* Define if you have the gif library (-lgif).  */
> #define HAVE_LIBGIF 1
> 
> But why would some lines be commented undefs while others are uncommented
> defines?  I don't see an instance of a commented define or an uncommented
> undefine. . . is there a lesson here?  Should I start plugging in explicit
> defines where there are now commented undefs?

If the line is a commented #undef, this means you don't have the library.
It is left commented so that you can override the setting with compile-time
defines (i.e., the -D compiler option).

Based on the above, you do have libgif, but you don't have libtiff.
That's a problem.  Raster has said before that E needs *all* of the
libs (tiff, png, gif, jpeg, z, m) to run.

Michael

-- 
 "Who needs women?  Give me gcc and a couple megs of source code, and
  I'm good for at least an hour or so...."
=======================================================================
Michael Jennings        http://www.tcserv.com/         <[EMAIL PROTECTED]>
Associate Tech Services Analyst I, Vencor IS     http://www.vencor.com/
-
To unsubscribe from this list send mail to: [EMAIL PROTECTED]
with the message contents: unsubscribe e-develop

Reply via email to