I do use LD_OPTIONS to use "-L libname -R libname", and I do use
"--with-png-includes=mypath/lib-png-1.2.5/include" with configure too.
Yet somehow it's using a png.h from libpng-1.0.1. The png.h in
'mypath/lib-png-1.2.5/include' is indeed the png.h from 1.2.5, and my
configure.log shows it finding the png.h from that directory and not
some other one.
this is really odd.
Ben
Dan Espen wrote:
Ben Sferrazza <[EMAIL PROTECTED]> writes:
Thanks for the fvwm-root suggestion. I think that seems to share the
cause of my troubles.
% fvwm-root ~/bin/fvwm-icons/dtterm.png
libpng warning: Application was compiled with png.h from libpng-1.0.1
libpng warning: Application is running with png.c from libpng-1.2.5
libpng error: Incompatible libpng version in application and library
[fvwm-root] failed to load image file '~/bin/fvwm-icons/dtterm.png'
I'm not quite sure why this would be happening. Perhaps it's finding
the libpng-1.0.1 png.h file from a system wide directory before finding
my local 1.2.5 png.h file. Maybe I just need to reorder my
LD_LIBRARY_PATH? Any suggestions?
You shouldn't try to use LD_LIBRARY_PATH.
Use "-R libname" during build, set it using LD_OPTIONS.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
