Kdevelop 2.0 cant compile

Tarjei Knapstad tarjeik at chemcon.no
Tue Sep 11 10:48:44 BST 2001


On Tue, 11 Sep 2001, Willy Gardiol wrote:
>
> Ok so i did BUT....
> i discovered that a program compiled with gcc 2.95.2.1 CANT find simbols in a
> shared library compiled with 3.0.x!
> i get tons of "unresolved wymbol Qt_xxxx::Qt_xxxxx()"
> when i try to compile (better say to link) with 2.95.2.1 and please note qt
> is build shared with 3.0.1 and the same linking works with 3.0.1 (but of
> course i get error in compiling, sigh!)
>
This is no surprise as 3.x is not binary compatible with 2.95. (or
RedHat's 2.96). As a result you will have to recompile all the libraries
you intend to link with, using your freshly installed gcc 3.x.

Personally, I've compiled and installed gcc 3.0 and all the other
libraries I use, in /usr/local, and the just set PATH, LD_LIBRARY_PATH,
and LD_RUN_PATH to point to my /usr/local stuff. Sometimes strange things
happen because of this (dynamically linked binaries suddenly linked with
the wrong libs because of the paths and so on).

Good luck!

-- 
Tarjei Knapstad


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop mailing list