Andrew Kirrage a �crit :
> 
> I have installed kde2 beta4 from the cooker, but kdevelop seems to be
> missing(looking at the kde site their seems to be a redhat package but not a
> mandrake specific one). I installed the kde1-compat and  kde1-compat -devel
> so i could run the older kdevelop(1.1) but I get this error message:
> 
> kdevelop: error in loading shared libraries: kdevelop: undefined symbol:
> __ti15KRestrictedLine
> 
> is there any other packages i have to install?

I suppose those 2 packages should suffice.

I have the same problem with KDE 1 apps (unresolved symbol for
__ti15KTopLevelWidget, etc.).

I suppose there is a problem with current packages in cooker for KDE 1
compatibility.
I think 'ti' is for TypeInfo ? So 'moc' was not run correctly during the
build of the packages ?

For example :

$ objdump -T /usr/lib/libkdeui.so.2 | grep KRestrictedLine
0005f93c g    DF .text  00000015  Base       
className__C15KRestrictedLine
00092cf4  w   DF .text  0000001b  Base       
__thunk_36__._15KRestrictedLine
0009dc40  w   DO .data  000000c8  Base        __vt_15KRestrictedLine
0005f854 g    DF .text  0000005d  Base        _._15KRestrictedLine
0005f8b4 g    DF .text  00000085  Base       
setValidChars__15KRestrictedLinePCc
0009dc20  w   DO .data  00000020  Base       
__vt_15KRestrictedLine.12QPaintDevice
0005f5f0 g    DF .text  000000aa  Base       
keyPressEvent__15KRestrictedLineP9QKeyEvent
0005f954 g    DF .text  00000031  Base       
invalidChar__15KRestrictedLinei
0005f69c g    DF .text  000000e8  Base       
initMetaObject__15KRestrictedLine
0009b4a8 g    DO .data  00000004  Base        _15KRestrictedLine.metaObj
00092d10  w   DF .text  00000017  Base       
metaObject__C15KRestrictedLine
0005f784 g    DF .text  000000cf  Base       
__15KRestrictedLineP7QWidgetPCcT2  

No 'ti' !

BUT :

$ objdump -T /usr/lib/libkdeui.so.3 | grep __ti15KRestrictedLine
001fbee4 g    DO .bss   00000010  Base        __ti15KRestrictedLine 

There was such a bug in a Mandrake RPM long ago for the QwSpriteField
library.

Reply via email to