Re: RFS: jabber transports and services
I've only looked at jabber-jit, but I see a couple of problems. It includes a copy of the jabber source in it. when it should use the jabber-dev package. I went through this same problem building the old icq transport for jabber. It seems upstream don't like to link outside the tarball.
and this below.
g++ -g -Wall -I. -I../jabberd -I/usr/include -DWPJABBER -I/usr/include -fPIC -c -o jit/server.o jit/server.cpp
g++ -g -Wall -I. -I../jabberd -I/usr/include -DWPJABBER -I/usr/include -fPIC -c -o jit/wp_client.o jit/wp_client.cpp
jit/wp_client.cpp: In member function `virtual void
jit/wp_client.cpp:149: error: `terror' has no non-static data member named `
jit/wp_client.cpp:149: error: too many initializers for `terror'
make: *** [jit/wp_client.o] Error 1
make: Leaving directory `/tmp/buildd/jabber-jit-1.1.6/jit'
make: *** [all] Error 2
make: Leaving directory `/tmp/buildd/jabber-jit-1.1.6'
make: *** [build-stamp] Error 2
On Thu, Aug 14, 2003 at 01:20:31PM -0600, Jamin W. Collins wrote:
> I'm hoping that one (or more) of the DDs here might be willing to
> sponsor one (or more) of the following packages. All of these have
> either an RFP or ITP filed for them. I have updated the ITP entries
> that where not filed by me and asked to assume the ITP, Evan (the
> original ITP filer in both cases) is amiable to this.