[kde-solaris] Building from 3.5.7

[Daniel Rawson]

Michael Lindig wrote:
> Daniel Rawson wrote:
>> Michael Lindig wrote:
>>> Daniel Rawson wrote:
>>>> I'm attempting to build from the modified 3.5.7 source code
>>>> that was provided by Michael Lindig (thanks!!!), but I'm having
>>>> problems with the dependency on libart_lgpl_2.
>>>> 
>>>> I'm running Solaris 10 (01/06) and using gcc 3.4.3 as the
>>>> compiler.  I re-built QT 3.3.8 and it is installed locally.
>>>> 
>>>> When I build kdelibs, it complains about
>>>> /usr/lib/libart_lgpl_2.so with a "Wrong ELFCLASS" message.  I
>>>> re-built libart_lgpl_2 (version 2.3.19) from source; when I use
>>>> the updated library, I get "Undefined symbol" errors on just
>>>> three of the "art_*" symbols:
>>>> 
>>>> Undefined                       first referenced symbol
>>>> in file art_free(void*)
>>>> ./.libs/libkdecore.so art_alloc(unsigned long)
>>>> ./.libs/libkdecore.so art_realloc(void*, unsigned long)
>>>> ./.libs/libkdecore.so
>>>> 
>>>> Any hints will be appreciated!!
>>> is there any -lart_lgpl_2 option at linking? Can you provide the
>>> entire linking command line where libkdecore.so was build? What
>>> are you environment options (CFLAGS, CXXFLAGS, CC, ...)?

> Dan,
> 
> here are the only link-commands where the art_lgpl_2 lib is used ?!

> 
> Did you use the SHELL=/bin/bash Environment? You may also do some
> adjustments with libtool for 64-bit development. I think you should
> better use the 32-bit environment, this simplifies something!
> 
> Hope this helps, Michael 
> 
> 
Michael -

Re-did everything as 32-bit and it's all working . . . . Thanks for your help (and your source code!)

Dan

-- 
The information contained in this communication and any attachments is confidential
and may be privileged, and is for the sole use of the intended recipient(s). Any
unauthorized review, use, disclosure or distribution is prohibited. If you are not
the intended recipient, please notify the sender immediately by replying to this
message and destroy all copies of this message and any attachments. ASML is neither
liable for the proper and complete transmission of the information contained in this
communication, nor for any delay in its receipt.