Hi, I'm seeing something similar here on RH 7.3. I've been building rpms from the daily snapshots for quite some time with no problems at all. However, the very day when libpng went to 1.2.1 in the ntop source, a problem did come up.
The rpms build fine, but when I try to install them I get a failure due to a dependency not being met for libpng.so.3. I just force install them with a --nodeps switch and they work fine, so I haven't looked into this any further. I do have the same link as you do: /usr/lib/libpng.so.3 -> libpng12.so.0.1.2.2. Looks like a packaging quirk here. >You are right, you're rambling <grin />... read on... > >On my Linux box, libpng.so.3 is a link to the real library: > >[bstrauss@tigger ntop-current]$ ls -l /usr/lib/libpng.so.3 >lrwxrwxrwx 1 root root 19 Apr 18 10:19 >/usr/lib/libpng.so.3 -> libpng12.so.0.1.2.2 > >Doing a cp will create a copy, not another link. If you then update libpng, >you have a version mismatch... > >The message - as described in the FAQ entry - occurs because RedHat (and >probably other distros although I decline to claim knowledge about them) >have already installed shared versions (.so) of the libpng libraries of >particular (peculiar) versions. > >That's why the standard ntop instructions tell you to build a STATIC version >(.a) of the libraries and links against that. You build STATIC against a >version, you run STATIC against the same version ... no mismatch errors. > >Somehow you didn't do that - get it all static - or the .so wouldn't have >mattered. > >Now I did notice that the file in the cvs still has the old version numbers >for zlib and libpng, so I'll update that. But the right versions were the >only ones present in the .tgz. (I just checked). > >Perhaps you commingled two downloads (one with the old versions) and then >did build 1.0.8 and 1.2.1? The Makefile does use 1.2.1 for the .h files... >that might cause the problem, but I'm still clueless about the .so issue, it >shouldn't have happened. > >Sorry, but in the absence of more info, if I haven't guessed correctly >above, I'm going to tag this as user error, given that 10s or 100s of people >have followed those instructions on a huge variety of distros w/o problem... > _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop
