On Monday 20 January 2003 2:15 pm, Peter B Van Campen wrote:
Dear Marshall,
No Go. I installed zlib-devel but config dies athe same way == on the png section as before.
Do you think the newness of the newer libpng is somehow wrong?
looking closely at the output we see:
"============ Checking for PNG support ============
#include
[...] gcc /tmp/mplayer-conf-6969-28776.c -o /tmp/mplayer-conf-3237-28776.o -lpng -lz -lm /tmp/mplayer-conf-6969-28776.c:1:17: png.h: No such file or directory
this error alone indicates that gcc cannot find the file "png.h" -- have you tried a "locate" or "find" against this file? I'm thinking that perhaps the name of the header file changed, or perhaps you've installed it in some way that you don't have read access to the file [or directory] [which would be weird] or the simplest explanation: something else clobbered the file and it is actually gone... If the file "png.h" does indeed exist, is it "where the compiler and/or ./configure script is looking for it?" This is a more likely case as [often] distribution maintainers think "they know better than the developer"(*) and move package installation points around -- in other words, the SuSE-specific "libpng(-devel)" package might not be in the same location that the straight-from-the-source package installs into. Tom (*) actually, this is more a case of balancing independant package maintainers against the common good -- SuSE might be right in moving a particular package "because where the maintainer placed it really is wrong" [i.e., doesn't match the majority of other packages or where a community consensus has been reached on the "right" place to put a package...]