Michael Jennings wrote:
> 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....) :)
Showoff. :P
I started off doing tarballs because the E sites generally pointed to them as opposed
to rpm's, but somebody else advised me to stick to rpm's. At any rate, many of the
libraries have been compiled 'by hand', all have been rpm'ed, therefore some have
gotten it from both ends, so to speak.
> > 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:
>
>
>
> 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).
This is curious. For example:
[root@fred /root]# file /usr/lib/libtif*
/usr/lib/libtiff.a: current ar archive
/usr/lib/libtiff.so: symbolic link to libtiff.so.3.4
/usr/lib/libtiff.so.3: symbolic link to libtiff.so.3.4
/usr/lib/libtiff.so.3.4: ELF 32-bit LSB shared object, Intel 80386, version 1, not
stripped
[root@fred /root]# ldconfig -v | grep tiff
libtiff.so.3 => libtiff.so.3.4
libtiff.so.3 => libtiff.so.3.4
>From the above, it seems to me that libtiff should show up as present on my box.
ldconfig also turns up entries for the gif, jpeg, and png libs, but only the gif lib
showed up as present in configure.h.
Does this mean that my libs are in funny places? If so, how do I pass that -D option
-- edit the makefile? Do I give absolute paths? (for example, gcc -D
/usr/lib/libpng.so.2.1.0)?
>
>
> 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.
Yup, caught that one myself, and at some point this afternoon all of the lib packages
he lists in README _did_ compile and install on my box -- at least as far as I could
tell. Since then I've run ldconfig several times and rebuilt imlib at least twice.
Still no joy.
But at least it does appear that we've got the problem tracked down. Definitely
something up with imlib, definitely compile problems. . . just no idea what to do.
Just before I got your last, I went through my config.h file and manually hacked all
the /* #undef . . . */ lines, uncommented them and replaced #undef with #define.
Having little or nothing to lose, I'm going to go ahead and try it that way and see
what disaster befalls.
Apparently, I never learn.
-
To unsubscribe from this list send mail to: [EMAIL PROTECTED]
with the message contents: unsubscribe e-develop
