On Fri, Aug 15, 2003 at 10:06:58AM +1000, Jason Thomas wrote: > 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.
The JIT package uses a trimmed version of the the wpjabber source, as indicated on the project's homepage: http://jit.jabberstudio.org/ which is not the same as the source used for the jabber or jabber-dev packages. Of the transport and service packages, it is the only one that does this that I've built so far. > 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 > WPclient::SignalDisconnected(ICQ2000::DisconnectedEvent*)': > jit/wp_client.cpp:149: error: `terror' has no non-static data member named ` > terror_struct::code' > jit/wp_client.cpp:149: error: too many initializers for `terror' > make[2]: *** [jit/wp_client.o] Error 1 > make[2]: Leaving directory `/tmp/buildd/jabber-jit-1.1.6/jit' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/tmp/buildd/jabber-jit-1.1.6' > make: *** [build-stamp] Error 2 I'm did not see that here with g++ v3.2.3: 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 gcc -g -Wall -I. -I../jabberd -I/usr/include -DWPJABBER -I/usr/include -fPIC -c -o utils/charset.o utils/charset.c gcc -g -Wall -I. -I../jabberd -I/usr/include -DWPJABBER -I/usr/include -fPIC -c -o utils/xdata.o utils/xdata.c Just upgraded to g++ v3.3.1 and now I get the same error. I've reported this to the jit upstream author. I've temporarily set gcc-3.2 and g++-3.2 as the defaults and added them as build depends for this package. A new revision of the package is now available. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
