I hate to reply to my own mail but ... > *** Warning: the command libtool uses to detect shared libraries, > *** /usr/bin/file, produces output that libtool cannot recognize. > *** The result is that libtool may fail to recognize shared libraries > *** as such. This will affect the creation of libtool libraries that > *** depend on shared libraries, but programs linked with such libtool > *** libraries will work regardless of this problem. Nevertheless, you > *** may want to report the problem to your system manager and/or to > *** [EMAIL PROTECTED] > > And it seems to appear because the /usr/bin/file command run on my > /lib/libc-2.1.3.so library produces > > /lib/libc-2.1.3.so: ELF 32-bit (SYSV) MSB shared object, PowerPC or > cisco 4500, > version 1, not stripped > > which fails when run through the egrep in line 2096 of ltconfig, which > on my system evaluates to > > egrep "ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )" > > Does anyone know if anything nasty will happen if I ignore this warning?
This was actually due to the version of /usr/bin/file I was using. The latest (as far as I know) version, file-3.35, produces: /lib/libc-2.1.3.so: ELF 32-bit (SYSV) MSB shared object, PowerPC or cisco 4500, version 1, not stripped but when run on the very same file, file-3.27 produces: /lib/libc-2.1.3.so: ELF 32-bit MSB shared object, PowerPC or cisco 4500, version 1, not stripped When ntop is compiled using file-3.35, there are a lot of warnings due to the extra (SYSV) which is not expected by ltconfig as noted above. When file-3.27 is used, ntop compiles cleanly. Hopefully this will save someone else some of the problems I had. Would someone who knows what they are doing like to take a stab at fixing ltconfig? I tried, but got errors when I tried to run ntop :( Tania _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listmanager.unipi.it/mailman/listinfo/ntop
