Hello Everyone, I'm having a problem installing kicq 2.0.0b1 in tarball. i got past ./configure, but when i ran make, i came across an error and kicq didn't install. I asked the developer of kicq, and he knew i was using debian because of the error. What seems to be the real problem, and how can it be fixed? Below is a snippet from the kicq mailing list:
----- SUBJECT: RE: [kicq-users] Re: kicq 2.0beta1 install problem (make) Joel Douglas Maxwell <<EMAIL: PROTECTED>> writes: > > > Well, after getting 20mb of packages, i got past the "./configure" stage. > > > Now i've come across an error in make: > > > > > > g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/include > > > -I/usr/include/kde -I/usr/lib/qt2/include -I/usr/X11R6/include > > > -I../../kicq -I../../kicq/chat -I../../kicq/contactlist > > > -I../../kicq/dialogs -I../../kicq/filetransfer -I../../kicq/history > > > -I../../kicq/info -I../../kicq/messageurl -I../../kicq/mydetails > > > -I../../kicq/preferences -I../../kicq/registration -I../../kicq/search > > > -I../../kicq/utils -I../../kicq/main -DQT_NO_ASCII_CAST -O2 > > > -fno-exceptions -fno-check-new -Wall -pedantic -W -Wpointer-arith > > > -Wmissing-prototypes -Wwrite-strings -Wno-long-long -fno-builtin -c > > > chatedit.cpp -fPIC -DPIC -o .libs/chatedit.o > > > chatedit.cpp: In method `void ChatEdit::keyPressEvent(QKeyEvent *)': > > > chatedit.cpp:46: `MW' undeclared (first use this function) > > > chatedit.cpp:46: (Each undeclared identifier is reported only once > > > chatedit.cpp:46: for each function it appears in.) > > > make[3]: *** [chatedit.lo] Error 1 > > > make[3]: Leaving directory `/usr/local/bin/kicq/kicq/chat' > > > make[2]: *** [all-recursive] Error 1 > > > make[2]: Leaving directory `/usr/local/bin/kicq/kicq' > > > make[1]: *** [all-recursive] Error 1 > > > make[1]: Leaving directory `/usr/local/bin/kicq' > > > make: *** [all-recursive-am] Error 2 > > > > > > Any clue as to what happened? > > > > Let me guess, you have Debian... > > Debian 2.2, with kernel 2.2.17 > what does this distro have to do with the problem, and how can it be > fixed? I don't know what problem is. Just Debian's gcc doesn't want to understand -I option. -- Denis V. Dmitrienko | E-mail: <EMAIL: PROTECTED> | ICQ#: 5538614 Home page: http://denix.org ----- End Of Snippet ----- what seems to be wrong with gcc? --Joel Maxwell
