Certain configure checks in tcpdump may pass when they really shouldn't, which leads to the compile failing because it links with symbols the configure script mistakenly thought were there (pcap_debug and yydebug are the two major offending symbols). We have gcc's new tricksy optimizations to thank for that.
A similar fix is already in tcpdump-cvs. -- Kelledin "If a server crashes in a server farm and no one pings it, does it still cost four figures to fix?"
Submitted By: Kelledin <kelledin at users dot sf dot net> Date: 2005-03-09 Initial Package Version: 1.0 Upstream Status: From upstream Origin: http://patches.linuxfromscratch.org Description: Certain configure checks in tcpdump-3.8.3 fail because gcc tends to optimize away critical parts of the test code. This patch works around the problem. diff -Naur tcpdump-3.8.3/configure tcpdump-3.8.3-pcap_debug/configure --- tcpdump-3.8.3/configure 2004-03-28 21:06:09.000000000 +0000 +++ tcpdump-3.8.3-pcap_debug/configure 2005-03-09 20:51:32.000000000 +0000 @@ -8888,7 +8888,7 @@ return pcap_debug; } - ; + return_pcap_debug(); return 0; } _ACEOF @@ -8947,7 +8947,7 @@ return yydebug; } - ; + return_yydebug(); return 0; } _ACEOF
-- http://linuxfromscratch.org/mailman/listinfo/patches FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
