Sorry for the cross-post but as I replied to someone who posted to the slackware forum with similar problems, I figured that, since I'm using LFS and it's a basic problem regarding libpng compiling, it needed to be addressed to a different audience, so here it goes.

Enlightenment shows this warning on startup:

libpng warning: Application is running with png.c from libpng-1.0.16
libpng error: Incompatible libpng version in application and library
IMLIB ERROR: Cannot load image: /usr/share/enlightenment/config/pix/mouse_1.png
All fallbacks failed.
libpng warning: Application was compiled with png.h from libpng-1.2.5
libpng warning: Application is running with png.c from libpng-1.0.16
libpng error: Incompatible libpng version in application and library
IMLIB ERROR: Cannot load image: /usr/share/enlightenment/config/pix/key_ctrl.png
All fallbacks failed.

etc.etc. for every png file Enlightenement tries to load, and since it's pretty much all png, the desktop is inefficient.

At first, I had mistakenly compiled the new 1.2.6 version when I should have compiled the 1.0 version. Enlightenment would then just crash X! Then I tried with libpng-1.0.16-config, but now all I get is the message shown earlier.

Then I thought that I had some 1.2 remnant in my system so I cleaned up every occurence of libpng (headers and libraries) from it. I even recompiled imlib and Enlightenment but I still have that same warning.

I would suspect that there is some sort of default setting to enable. This package's Makefile has an entry called LIBPNG12_VERSION_INFO = @LIBPNG12_VERSION_INFO@. This is obviously misleading but libpng cannot compile without replacing some sort of integer there, possibly an env variable. I've tried many of them, 0,1,10, etc., with the same results. I guess they are using the same tree for the two versions but I'm a victim of some mismatch.

I don't believe this is an imlib error. The warning comes from libpng and imlib is just responding to it.

Feel free to repond and thanks for any help.