I have included diffs for the changes I've made to the jabberd server. The primary changes are to make it play with all kinds of make, not just gnumake, and to make it play with ansi-C compilers. Oh, and also to make it work with HP-UX, but I didn't hard-code the required pth parameters, as I built pth separately. Makefile changes: 1) ifeq is a gmake-ism. recoded to not use it. 2) CFLAGS:=$(CFLAGS) is also a gmake-ism. 3) I changed the CC lines that did links to LD, because a) they *are* links, and b) because my CC tried to pull in crt.o. ANSI C changes: 1) (terror){400, "Bad Request"} is not ansi C. I defined a macro that leaves things alone for gcc, but calls a function otherwise. I noticed that there were several places in jsm where the terror messages had duplicate numbers. I added these as is to jabberd/lib/lib.h, but someone might want to make up new numbers. I don't know enough to know if that's a good idea, so I didn't do it. 2) (At least HP's) ansi C doesn't like using return with a function that returns a void (jabberd/deliver.c: return deliver_internal(p, i) ). I separated this into two statments. 3) HP's ansi C didn't like cur->cur +=len in jabberd/mio.c, so I changed it to an explicit add. 4) HP's ansi C didn't like run-on lines with no "\" at the end, for example in jabberd/mio_xml.c, so I added "\n\" to the end of each line. Finally, there is a completely spurious change in configure: For some reason, printf "Getting pth settings..." cores printf. Add 1 character, subtract one character, it is fine. Go figure. But print works just dandy, so I changed it. ==Doug Claar, doug@claar.org Info about me: I work at HP. Messing with jabber isn't my day job. But I want a way for our group to communicate that doesn't go outside the firewall, I don't like AOL much anyway, and jabber's cool.