Yes, I have compiled tcpdump with new path of the libpcap library without any issue.
root@beagleboard:/mnt/tcpdump-4.5.1/build# > /mnt/tcpdump-4.5.1/build/binaries/sbin/tcpdump -h > tcpdump version 4.5.1 > libpcap version 1.5.2 I think this issue was appeared because before to compile libpcap library I have compiled several another packages already and may one of them has made any changes in the my environment. Hope it will not appear again. On Tue, Dec 24, 2013 at 11:19 PM, Guy Harris <g...@alum.mit.edu> wrote: > > On Dec 24, 2013, at 1:11 PM, Evgheni Antropov <aid...@gmail.com> wrote: > > > You are absolutely right in it. > > I have tried again to compile libpcap 1.5.2 in the new directory and it > was done with success. > > > > root@beagleboard:/mnt/libpcap-1.5.2/build# file > /mnt/libpcap-1.5.2/build/binaries/lib/libpcap.so.1.5.2 > > /mnt/libpcap-1.5.2/build/binaries/lib/libpcap.so.1.5.2: ELF 32-bit LSB > shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, > BuildID[sha1]=5cab06ddf6ba7e042de65048f5cfd969ed6536b1, not stripped > > ...and you were able to link tcpdump with the resulting libpcap? > > If so, there were probably one or more bad .o files in the directory when > you did the build, as your libpcap_configure file didn't show any > compilation being done, just linking into a .so file and archiving into a > .a file, and doing the "make distclean" cleaned that up. _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
