Re: [squid-users] Re: my "CPPUNIT" is "broken"... ;-) ?

Henrik Nordstrom wrote:
> Copy-pasted your configure line on my Fedora Core 5 test 3 x86_64 box,
> and it compiles just fine..

---
Figures.
> 1. Grab the current snapshot release.
---
	Ahead of you.  Already done (squid-3.0-PRE3-200603017.tar.bz2).
> 2. Start with just ./configure, without any arguments.
---
	Tried that too.  The configure completes with no error message in
either case.   It's the "make" that follows that displays the error when
it gets to cppunit.  From the make I traced back to what it was complaining about:
...
Making all in cppunit
make[4]: Entering directory `/home/tools/squid/work/lib/cppunit-1.10.0/src/cppunit'
/bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. 
-I../../config -I../../include -I../../include    -g -O2 -c -o 
AdditionalMessage.lo AdditionalMessage.cpp
mkdir .libs
  g++ -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../../include -g 
-O2 -c AdditionalMessage.cpp  -fPIC -DPIC -o .libs/AdditionalMessage.o
In file included from ../../include/cppunit/Portability.h:10,
                  from ../../include/cppunit/Message.h:4,
                  from ../../include/cppunit/AdditionalMessage.h:4,
                  from AdditionalMessage.cpp:1:
../../include/cppunit/config-auto.h:12:17: warning: extra tokens at end of 
#ifndef directive
...many of these...
In file included from ../../include/cppunit/Message.h:4,
                  from ../../include/cppunit/AdditionalMessage.h:4,
                  from AdditionalMessage.cpp:1:
../../include/cppunit/Portability.h:205:5: #error Cannot define 
CppUnit::OStringStream.
make[4]: *** [AdditionalMessage.lo] Error 1
make[4]: Leaving directory `/home/tools/squid/work/lib/cppunit-1.10.0/src/cppunit'
make[3]: *** [all-recursive] Error 1
---
	That traced back to what appears to be bogus code in 'config-auto.h'.
What should that file look like, anyway?  Seems like something in 'configure'
should be producing it.
> 3b, If a plain configure fails, dig into the config.log files to try to
> identify what it going wrong. If it still fails within cppunit the
> config.log to stare at is lib/cppunit-1.10.0/config.log and match this
> to the configure script in the same directory.
---
	Configure isn't giving an error message.  It seems to complete with
no error.  The last line in the config.log of "cppunit" (the nested configure)
is "configure: exit 0", which looks like an "ok" exit status.
	I'll poke around more, maybe an empty config in cppunit...etc....
Cheers,
-linda