<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.3698" name=GENERATOR><LINK
href="BLOCKQUOTE{margin-Top: 0px; margin-Bottom: 0px; margin-Left: 2em}"
rel=stylesheet></HEAD>
<BODY
style="MARGIN-TOP: 10px; FONT-SIZE: 10pt; MARGIN-LEFT: 10px; COLOR: #000000; MARGIN-RIGHT: 10px; FONT-FAMILY: Verdana">
<DIV>Hi Jeremy,</DIV>
<DIV> </DIV>
<DIV>Here is my experience:</DIV>
<DIV> </DIV>
<DIV>The first time, (1)I used the following values for parameters for 'configure':</DIV>
<DIV><FONT
color=#000080><EM>./configure --prefix=/home/software/bind10 --with-lcov=/home/software/lcov/usr/bin/lcov --with-gtest=/home/software/gtest --disable-setproctitle-check</EM></FONT></DIV>
<DIV>(2)Then ran '<EM><FONT
color=#000080>make</FONT></EM>'. No error information at all.</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>(3)Then<EM><FONT
color=#000080>./configure --prefix=/home/software/bind10 --with-lcov=/home/software/lcov/usr/bin/lcov --disable-setproctitle-check</FONT></EM></DIV>
<DIV>(4)when running 'make':</DIV>
<DIV><EM><FONT
color=#000080>run_unittests-data_unittests.o: In function `(anonymous namespace)::Element_to_and_from_wire_Test::TestBody()':</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>/home/software/bind10-devel-20101201/src/lib/cc/tests/data_unittests.cc:385: undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResultType, char const*, int, char const*)'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>/home/software/bind10-devel-20101201/src/lib/cc/tests/data_unittests.cc:386: undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResultType, char const*, int, char const*)'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>/home/software/bind10-devel-20101201/src/lib/cc/tests/data_unittests.cc:387: undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResultType, char const*, int, char const*)'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>/home/software/bind10-devel-20101201/src/lib/cc/tests/data_unittests.cc:388: undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResultType, char const*, int, char const*)'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>/home/software/bind10-devel-20101201/src/lib/cc/tests/data_unittests.cc:389: undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResultType, char const*, int, char const*)'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>run_unittests-data_unittests.o:/home/software/bind10-devel-20101201/src/lib/cc/tests/data_unittests.cc:390: more undefined references to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResultType, char const*, int, char const*)' follow</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>collect2: ld returned 1 exit status</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[6]: *** [run_unittests] Error 1</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[6]: Leaving directory `/home/software/bind10-devel-20101201/src/lib/cc/tests'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[5]: *** [all-recursive] Error 1</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[5]: Leaving directory `/home/software/bind10-devel-20101201/src/lib/cc'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[4]: *** [all] Error 2</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[4]: Leaving directory `/home/software/bind10-devel-20101201/src/lib/cc'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[3]: *** [all-recursive] Error 1</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[3]: Leaving directory `/home/software/bind10-devel-20101201/src/lib'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[2]: *** [all-recursive] Error 1</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[2]: Leaving directory `/home/software/bind10-devel-20101201/src'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[1]: *** [all-recursive] Error 1</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make[1]: Leaving directory `/home/software/bind10-devel-20101201'</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>make: *** [all] Error 2</FONT></EM></DIV>
<DIV></DIV>
<DIV> </DIV>
<DIV>======================================================</DIV>
<DIV>The second time, I used the
same values for parameters for configure:</DIV>
<DIV><EM><FONT
color=#000080>configure with some values</FONT></EM></DIV>
<DIV><EM><FONT color=#000080>make</FONT></EM></DIV>
<DIV><EM><FONT color=#ff0000>make clean</FONT></EM></DIV>
<DIV><EM><FONT
color=#000080>configure with other values</FONT></EM></DIV>
<DIV><EM><FONT color=#000080>make</FONT></EM></DIV>
<DIV>All is OK.</DIV>
<DIV> </DIV>
<DIV>I think it does no harm that bind10 can run 'make clean' automatically
when the 'configure' statement has changed.^_^</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV></DIV>
<DIV>>On Mon, 20 Dec 2010, Mary wrote:</DIV>
<DIV>></DIV>
<DIV>>> BTW: I'd strongly recommend that a 'make clean' command should be </DIV>
<DIV>>> executed automatically when necessary( e.g. the parameters for </DIV>
<DIV>>> configure have changed?. I've heard that bind 9.7 does something like </DIV>
<DIV>>> this in 'configure'</DIV>
<DIV>></DIV>
<DIV>>Can you share a specific example (maybe copy and paste error output) of </DIV>
<DIV>>why you think this is needed?</DIV>
<DIV>></DIV>
<DIV>>We probably should fix case-by-case make issues versus starting </DIV>
<DIV>>over.</DIV>
<DIV>></DIV>
<DIV>> Jeremy C. Reed</DIV>
<DIV>> ISC</DIV>
<DIV></DIV>
<DIV>= = = = = = = = = = = = = = = = = = = =</DIV></BODY></HTML>