According to Jason Buchanan: > Using gcc version 3.0.1: > > make[1]: Leaving directory `/usr/src/htdig- > 3.2.0b4-100701/htdb' > Making all in htdig > make[1]: Entering directory `/usr/src/htdig- > 3.2.0b4-100701/htdig' > c++ -DHAVE_CONFIG_H -I. -I. -I../include - > DDEFAULT_CONFIG_FILE=\"/www/htdig/conf/htdig.conf\ > " -I../include - > I../htlib -I../htnet - > I../htcommon -I../htword - > I../db -I../db - > I/usr/local/include -O3 -mcpu=i686 -Wall -fno- > rtti -fno-exceptions -c Document.cc > In file included from Document.h:34, > from Document.cc:31: > ExternalTransport.h:29: friend declaration > requires class-key, i.e. `friend > class ExternalTransport' > make[1]: *** [Document.o] Error 1 > make[1]: Leaving directory `/usr/src/htdig- > 3.2.0b4-100701/htdig' > make: *** [all-recursive] Error 1 > > > It's very unhappy ;-) This carries through > several of the htdig snapshots... not just this > specific one.
Thanks! This is a pretty easy one. Just edit htdig/ExternalTransport.h, and on line 29, add the word "class" right after the word "friend", and before the word "ExternalTransport", pretty much as the error message suggests. That should get past this one sloppy declaration and get to compiling other things. (Next Sunday's snapshot will have this.) It will undoubtedly fail somewhere else, though. Based on one or two other error messages I've received, it seems gcc 3.0's C++ compiler is very picky about things, and I'm sure we haven't heard the last of these problems. Oddly enough, not all gcc 3.0 users are getting the same errors when compiling htdig. Hopefully we'll whittle the problems away one by one. > According to Mark Alexander: > > Sorry - Don't have gcc 2.95 use any more - all > my other programs compile > > under 3.0. > > > > Will live with the current situation, until > another version is > > released. > > This is the problem. Everyone seems to want to > wait until Geoff or I fix > everything. Well right now, Geoff and I don't > use gcc 3.0, so unless someone > with gcc 3.0 shows some willingness to help us > figure out what needs to be > changed in the code to make it compile, the next > version isn't going to be > any more gcc-3.0-compliant than the current > version. > > > > "Geoff Hutchison" <[EMAIL PROTECTED]> > 09/04/01 06:47a.m. > > > > > At 8:46 AM +1200 8/29/01, Mark Alexander wrote: > > >Tryed compiling 3.1, no luck. Tryed 2.95, no > > >luck. Installed 2.95 binaries, same problem > > >compiling htdig. > > > > And the exact error messages from gcc/g++ were? > With the 2.95 > > release, I'm assuming you've tried compiling > other C++ programs and > > they're fine? > > So, what's up with gcc 3.0? Are exact error > messages and a bit of assistance > too much to ask? -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
