[kaffe] kafee-qt 1.0.7 for ipaq on a board like assabet

Dalibor Topic robilad at yahoo.com
Tue Jun 3 16:53:01 PDT 2003

Hi Sankalpa,

--- Sankalpa <sgamwarige at sri.crossvue.com> wrote:
> Hi
> 	I have successfully ported linux 2.4.18 rmk 7 to a customised board
> like assabet.I managed to up qt 2.3.2 with ipaq configuration (doing
> some minor modifications to suite to my system touch screen driver).Now
> I can run example aplications in qt 2.3.2 very well.
> 	To up kaffe on my machine I downloaded kaffe-qte_1.0.7-0.1_arm.ipk and
> extracted them to /opt directory and added /opt/Q*/bin to my path.
> 	So I managed to run simple Hello.class java program.

Are you sure you got that ipk file from kaffe.org?

> I tried to run simple awt applications in following ways.
> 1.with winmanager -qws& up and qt lib path is added to my
> 2.without winmanager up.

What's a winmanager?
> In both occations I got following error.
> # java Panel1
> java.lang.ExceptionInInitializerError: [exception was
> java.lang.UnsatisfiedLinkError: libawt: not found]
>         at java.awt.Button.<init>(Button.java:44)
>         at java.awt.Button.<init>(Button.java:36)
>         at Panel1.<init>(Panel1.java:18)
>         at Panel1.main(Panel1.java:40)
> java.lang.UnsatisfiedLinkError: libawt: not found
>         at java.lang.Throwable.fillInStackTrace(Throwable.java:native)
>         at java.lang.Throwable.<init>(Throwable.java:38)
>         at java.lang.Error.<init>(Error.java:21)
>         at java.lang.LinkageError.<init>(LinkageError.java:21)
>         at
> java.lang.UnsatisfiedLinkError.<init>(UnsatisfiedLinkError.java:21)
>         at java.lang.Runtime.loadLibrary(Runtime.java:150)
>         at java.lang.System.loadLibrary(System.java:142)
>         at java.awt.Button.<init>(Button.java:44)
>         at java.awt.Button.<init>(Button.java:36)
>         at Panel1.<init>(Panel1.java:18)
>         at Panel1.main(Panel1.java:40)
> Further I searched for libawt.*.so and added that path to LD_LI*RY_PATH
> but result is same.
> What may be the problem?

Dynamic linking of libawt fails. Read FAQ/FAQ.debugging and use gdb to figure
out what's really happening. Set a breakpoint on loadNativeLibrary and see if
you can find out what's the exact cause for the breakage.

There are so many ways for linking of c++ libraries to fail, it's not even
funny (bad moc version in path, bad QTDIr setting, bad QTEDIR setting, wrong
compiler ABI version, and whatever makes qt awt fail on my suse box right now
wtihout leaving a stack trave in the debugger while it works on my mandrake
box, or as the most bizarre cause I've seen with qt-embedded: not piping std*
streams to /dev/null ). Without going over through it using gdb, there is no
way you can find out what's the cause du jour ;)

I assume you should first ask wherever you got that ipk file from. I, for
example, don't even know what an ipk file is ;)

good luck hunting the problem down,
dalibor topic

Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).

More information about the kaffe mailing list