Re: Fishing for advice...

Shaw Terwilliger (sterwill@postman.abisource.com)
Wed, 23 Jun 1999 10:09:54 -0500


On Wed, Jun 23, 1999 at 08:08:53AM -0400, tw@rcinet.com wrote:
> Is expat supposed to spew warnings? It compiles, but that many warnings makes me nervous.

Yeah, expat has some warnings, but it's a very tested piece of software
(it's the XML engine behind Mozilla, Netscape, AbiWord) and we've only had
very minor issues with its parsing (mostly non-Latin 1 chars that do/don't
need to be escaped).

The reason it's throwing many of those errors (and the same reason applies
to things like mswordview) is that we're using C++ compiler flags on
code used to C rules. C++ has become more strict in what it allows
but most compilers are smart enough to sense when things are meant
to be used in a C world.

> Abi also spews warnings when compiling. I mean loads and loads of warnings. I presume this is somewhat normal or am I screwing something up. I am using RedHat 6.0 and just going into abi/src and typing make. (This is after compiling expat.)

> Hell I was thinking about taking a look at some of the warnings and fixing a few "ANSI C++ forbids..." errors.

I believe that's all mswordview code, which is a package we just based
our importer on. We have a crew (Justin Bradford and me, really) writing
a new importer using mswordview as a library interface; it should be
much cleaner and shouldn't spew 10 pages of warnings.

Our code certainly needs some cleanup somewhere. Usually what it takes
is doing "man [function]" where [function] is something undeclared, and
seeing which header file we didn't include.

> OK. I did a compile and it wrecks here... Anyone have a clue?
> .............................................................................
> make[3]: Entering directory `/home/tw/abisource/abi/src/wp/ap/unix'
> Building with [LicensedTrademarks:Off Debug:Off].
> ap_UnixApp.cpp:
> ap_UnixApp.cpp: In method `UT_Bool AP_UnixApp::initialize()':
> ap_UnixApp.cpp:99: warning: unused variable `UT_Bool bVerified'
> ap_UnixApp.cpp: In method `UT_Bool AP_UnixApp::parseCommandLine()':
> ap_UnixApp.cpp:510: no matching function for call to `AP_BuiltinStringSet::dumpBuiltinSet (char[13])'
> make[3]: *** [/home/tw/abisource/abi/src/../src/Linux_2.2.5-15_i386_OBJ/obj/ap_UnixApp.o] Error 1
> make[3]: Leaving directory `/home/tw/abisource/abi/src/wp/ap/unix'
> make[2]: *** [build] Error 2
> make[2]: Leaving directory `/home/tw/abisource/abi/src/wp/ap'
> make[1]: *** [build] Error 2
> make[1]: Leaving directory `/home/tw/abisource/abi/src/wp'
> make: *** [build] Error 2
> .............................................................................

I can't really tell here... it looks like you might have a half baked build.
You said you did try a recent CVS checkout; you might try it again if
you were using "cvs update" to grab it. You may also want to do "make clean"
or "make realclean" to see if it cleans out old objects. I just checked
a tree out (during writing this message) on one of our faster machines and
it built all the way through.

-- 
Shaw Terwilliger


This archive was generated by hypermail 1.03b2.