You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

asgar

Beginner

  • "asgar" started this thread

Posts: 3

Location: poland

  • Send private message

1

Wednesday, May 5th 2004, 7:32am

QString problem

I try to compile program called kbear and i recive these errors
.libs/kbearftp.o(.text+0x105): In function `kdemain':
: undefined reference to `QString::setNum(long long, int)'
The authors of kbear are not answer for my questions about it
maybe here someone will help me
i have seached the web but solustions like
qmake -project
qmake
make
dosn't work.(i mean ./configure;qmake -project;qmake;make)
may you help me
thanks

e8johan

Beginner

Posts: 27

Location: Sweden

  • Send private message

2

Wednesday, May 5th 2004, 7:36am

RE: QString problem

Are you sure that your Qt setup is sane? The method exists: http://doc.trolltech.com/3.2/qstring.html#setNum .

asgar

Beginner

  • "asgar" started this thread

Posts: 3

Location: poland

  • Send private message

3

Wednesday, May 5th 2004, 8:32am

RE: QString problem

thanks for answer.the errors loks like that:
.libs/kbearftp.o(.text+0x105): In function `kdemain':
: undefined reference to `QString::setNum(long long, int)'
.libs/kbearftp.o(.text+0x1458): In function `KBearFtp::readresp()':
: undefined reference to `QString::setNum(long long, int)'
.libs/kbearftp.o(.text+0x2ca7): In function `KBearFtp::openConnection()':
: undefined reference to `QString::setNum(long long, int)'
.libs/kbearftp.o(.text+0x8337): In function `.L2637':
: undefined reference to `QString::setNum(unsigned long long, int)'
.libs/kbearftp.o(.text+0x8d92): In function `.L2875':
: undefined reference to `QString::setNum(unsigned long long, int)'
.libs/kbearftp.o(.text+0x981a): In function `.L3126':
: undefined reference to `QString::setNum(unsigned long long, int)'
.libs/kbearftp.o(.text+0xc699): In function `KBearFtp::ftpSendCmd(QCString const&, int)':
: undefined reference to `QString::setNum(long long, int)'
.libs/kbearftp.o(.text+0xd70d): In function `KBearFtp::ftpOpenPASVDataConnection()':
: undefined reference to `QString::setNum(unsigned long long, int)'
.libs/kbearftp.o(.text+0x10eda): In function `KBearFtp::stat(KURL const&)':
: undefined reference to `QString::setNum(long long, int)'
.libs/kbearftp.o(.text+0x16ece): In function `KBearFtp::put(KURL const&, int, bool, bool)':
: undefined reference to `QString::setNum(unsigned long long, int)'
collect2: ld returned 1 exit status
make[3]: *** [kio_kbearftp.la.closure] Error 1
.my system is : debian sid
i have installed qt-x11-free-3.3.1.tar.bz2
and it has ended with message about succesfull compilation
in /etc/profile i added before compilation of qt
QTDIR=/usr/local/qt
PATH=$QTDIR/bin:$PATH
MANPATH=$QTDIR/doc/man:$MANPATH
LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
export QTDIR PATH MANPATH LD_LIBRARY_PATH
my system is DEBIAN SID
.i'm rather beginner.and this link is only ocumentation of qstrings functions.
do you have any ideas what can be wrong.it maybe looks like he is not saneof these functions(this only my interpretation).in documentaytion of qt they write that i don't have to use any flags for ./configure
i have read that sometimes instaling libqt3-compat-headers_3.2.3-2_all.deb
may help.but it didn't.
what do you think about it?

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

4

Wednesday, May 5th 2004, 5:05pm

It may be a problem with "long long", there is no method matching this type in QString

Cheers,
_
Qt/KDE Developer
Debian User

dfaure

Beginner

Posts: 16

Location: France

  • Send private message

5

Tuesday, May 11th 2004, 7:04am

There is (a method with long long), but only in recent Qt versions.
So I think the problem here is that the Qt headers being used don't match the Qt lib being used. Check the output of configure (where it looks for Qt), compare the -I paths with the -L paths to find the difference, or append -Q -v -Wl,-t to the link line to see exactly which libs it's using.
David Faure, KDE developer, Klaralvdalens-Datakonsult AB.