Date: Tue, 20 Jul 1999 22:40:15 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Alex Zepeda <garbanzo@hooked.net> Cc: eT <eT@post.com>, Hackers FreeBSD <hackers@freebsd.org> Subject: Re: KDE on FreeBSD (missing symbols) Message-ID: <Pine.BSF.4.10.9907202239300.58023-100000@salmon.nlsystems.com> In-Reply-To: <Pine.BSI.3.95.990720110232.18807B-100000@fish.hooked.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Jul 1999, Alex Zepeda wrote: > On Tue, 20 Jul 1999, eT wrote: > > > Greets .. I decided to compile KDE-1.1.1 for my 4.0-CURRENT. > > After compiling all (kde-1.1 and qt-1.44) I get the following errors when > > startx'ing: > > > > ld-elf.so complains about not finding these symbols: > > __ti6QFrame > > __ti7QObject > > __ti7Qblahblahblah > > > > I pressume there is something wrong with the way I compiled qt-1.44? > > You've gotta choose between the lesser of two evils. First, Qt 1.44 is > *not* recommended you should use Qt 1.42. Second of all, TT's support of > FreeBSD sucks, the FreeBSD port of Qt sucks. TT has enabled -fno-rtti > which causes problems for applications (such as KDE apps) that aren't > compiled with -fno-rtti. The FreeBSD port still suffers from this, as > well as depending on Mesa(?!). > > With whatever Qt version you're using go into the appropiate > configs/freebsd-... file and remove -fno-rtti. Who maintains the FreeBSD qt port? Perhaps you should fix the problems in the port and submit them as patches to the maintainer (and TT). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9907202239300.58023-100000>