Skip to main content

UnsatisfiedLinkError!!!

42 replies [Last post]
pigboy
Offline
Joined: 2006-03-08

i compiled the cvm by type
make CVM_TARGET_TOOLS_PREFIX= arm-linux - QT_TARGET_DIR=/usr/lib/qt-2.3.10 X11_DIR_LIB=/usr/X11R6/lib AWT_LIB_LIBS= J2ME_CLASSLIB=basis bin

i can successed in make the cvm,
./bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar

but when i run i my target device , it throws out the UnsatisfiedLinkError!!!
of libqtawt.so........

i check the cvm_runtime_guaid ,and know maybe it says i have to locate the Qt path or something , the running the personal profile or personal basis profile ...

can some one tell me how to do that , and what is the use of the lib_library_path ,,

Thanks!!!

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
pigboy
Offline
Joined: 2006-03-08

today , i download the qtopia-1.7.0 .rpm from the internet , and can run on my computer ,but copy the libqte.so to my qte-2.3.7,and compile the cvm, but i can't run the cvm.
Why ,is that?
If i need to compile the qte and qtopia for my device ,what can i do ?
the fellow is my document comes with the cross-compile from the GXcompany.

Compile QTE and Qtopia for OURSELEC:

Version: qte 2.3.7, qtopia 1.7.0 all are free version.
Created by Figo. 2006-07-04

----------------------------------------------------------------------------------------------

Prepare:

1. Make sure that install the toolchain provided in the CD package, please refer to the Linux user' guide.

2.

get tslib.tar.bz2

get tmake-1.11.tar.gz

get qt-embedded-2.3.7.tar.gz

get qtopia-free-1.7.0.tar.gz

Untar the source to work directory, this assume the work directory is /work .

for example : tar -jxf tslib.tar.bz2

tar vxzf tamke-1.11.tar.gz

rename the directory name "qtopia-free-1.7.0" to "qtopia-1.7.0"

Step 0:

export QTDIR=/work/qt-2.3.7

export QPEDIR=/work/qtopia-1.7.0

export LD_LIBRARY_PATH=/work/qt-2.3.7/lib:$LD_LIBRARY_PATH

export TMAKEDIR=/work/tmake-1.11

export TMAKEPATH=/work/tmake-1.11/lib/qws/linux-arm-g++

export PATH=/work/tmake-1.11/bin:$PATH

Step 1:

%cd tslib

%export CC=arm-linux-gcc

%./autogen.sh

%./configure --host=arm-linux

%make

%cp -a src/.libs/* ../qt-2.3.7/lib/

%cp -a plugins/.libs/*.so ../qt-2.3.7/lib/

Step 2:

%cd $QTDIR

(copy the qt_patch files to overwrite current files.)

%cp /work/qtopia-1.7.0/src/qt/qconfig-qpe.h /work/qt-2.3.7/src/tools/

%./configure -xplatform linux-arm-g++ -qconfig qpe

(color depth: 16 ; Virtual Framebuffer: no)

% make sub-src

Step 3 :

cp /usr/local/arm-linux/qt_toolchain/qt-2.3.2/bin/uic /work/qt-2.3.7/bin

export LD_LIBRARY_PATH=/usr/local/arm-linux/qt_toolchain/qt-2.3.2/lib:$LD_LIBRARY_PATH

.........

but i meet errors when i did the step 1,..make ...
i meet the problems of .......

make[2]: Leaving directory `/arm-target/zlib/src'
Making all in plugins
make[2]: Entering directory `/arm-target/zlib/plugins'
if /bin/sh ../libtool --mode=compile --tag=CC arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -MT linear.lo -MD -MP -MF ".deps/linear.Tpo" -c -o linear.lo linear.c; \
then mv -f ".deps/linear.Tpo" ".deps/linear.Plo"; else rm -f ".deps/linear.Tpo"; exit 1; fi
mkdir .libs
arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -MT linear.lo -MD -MP -MF .deps/linear.Tpo -c linear.c -fPIC -DPIC -o .libs/linear.o
/bin/sh ../libtool --mode=link --tag=CC arm-linux-gcc -rpath -o linear.la -module -avoid-version linear.lo
libtool: link: only absolute run-paths are allowed
make[2]: *** [linear.la] Error 1
make[2]: Leaving directory `/arm-target/zlib/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/arm-target/zlib'
make: *** [all] Error 2

...please help me!
Thanks!

Winson

Hinkmond Wong

Hi Winson,

> but i meet errors when i did the step 1,..make ...
> i meet the problems of .......
>
> make[2]: Leaving directory `/arm-target/zlib/src'
> Making all in plugins
> make[2]: Entering directory `/arm-target/zlib/plugins'
> if /bin/sh ../libtool --mode=compile --tag=CC arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -MT linear.lo -MD -MP -MF ".deps/linear.Tpo" -c -o linear.lo linear.c; \
> then mv -f ".deps/linear.Tpo" ".deps/linear.Plo"; else rm -f ".deps/linear.Tpo"; exit 1; fi
> mkdir .libs
> arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -MT linear.lo -MD -MP -MF .deps/linear.Tpo -c linear.c -fPIC -DPIC -o .libs/linear.o
> /bin/sh ../libtool --mode=link --tag=CC arm-linux-gcc -rpath -o linear.la -module -avoid-version linear.lo
> libtool: link: only absolute run-paths are allowed
> make[2]: *** [linear.la] Error 1
> make[2]: Leaving directory `/arm-target/zlib/plugins'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/arm-target/zlib'
> make: *** [all] Error 2

I'm sorry. This is beyond my knowledge and experience. It is not a
Java ME problem. Instead, it's a GenXin problem with their
cross-compile instructions and Makefiles for their libqte.so/libqpe.so.
You have to build following their instructions so that you have a
cross-compile version of libqte.so and libqpe.so for their device. You
cannot link with the Linux/x86 version of libqte.so and libqpe.so. That
will not run on your device that way.

You will have to contact GenXin for help. We do not have that
information here at Sun Microsystems on how to build their cross-compile
libraries.

Sorry, I cannot be of more help. Good luck! Let us know if GenXin
gives you a bug fix or corrects their Makefiles or instructions.

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

Thanks ! Hinkmond , i will if i make any progress or any information from the Gexin Company!

Winson

pigboy
Offline
Joined: 2006-03-08

I renew the linux system ,and it successed in compiling the qte-2.3.7 with depth 4,8,16,24,32,
but when i try it in the device , it's still show can drive 32!!
So i am a little confuse , because my device it's preinstall qtopia-1.7.0,with 16 depth, so it's this means i have to renew the qtopia-1.7.0 with depth of 32,or other optional depth? Or i have to reinstall the whole system for my target device with a qtopia with 32 ?

Hinkmond Wong

phonemeadvanced@mobileandembedded.org wrote:
> I renew the linux system ,and it successed in compiling the qte-2.3.7 with depth 4,8,16,24,32,
> but when i try it in the device , it's still show can drive 32!!
> So i am a little confuse , because my device it's preinstall qtopia-1.7.0,with 16 depth, so it's this means i have to renew the qtopia-1.7.0 with depth of 32,or other optional depth? Or i have to reinstall the whole system for my target device with a qtopia with 32 ?

That's a question for GenXin to answer since the question is not about
phoneME or Java.

GenXin will know best about how to obtain and compile the correct
libqte.so and libqpe.so for their device and how to use their
pre-installed version of the qtopia-1.7.0 library.

Sorry, since no one here on this mail alias has the device information
on what exactly GenXin has pre-installed on their device or how they
built their Linux system, we cannot help you.

Maybe there is a GenXin developers forum group you can join to help you
with these questions.

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

long time no trouble you .i am back.

Yes, it's the GeXin comany duty ,but they only provide us the qt-1.7.0 with the depth of 16, and i build the qt-1.7.0 with depth of 4,8,16,24,32, and meet two problems ,first it's the calibrate , when it start i didn't pass the calibrate or something we have to locate the touch mouse coordinate (so the we mouse coordinate is not correct)? but my qt-1.7.0 just pass through , can display the desktop of the qt,(it's ok as long as we can run the new qt on my device ), the second problems is .. when i run the cvm with the example of DemoXlet ,the whole screen become blank ,and graduately display the DemoXlet ,but when i touch the screen , it disappear. why ? i think this is not the qt depth problems any more.

Winson

Hinkmond Wong

Hi Winson,

phonemeadvanced@mobileandembedded.org wrote:
> long time no trouble you .i am back.
>
> Yes, it's the GeXin comany duty ,but they only provide us the
> qt-1.7.0 with the depth of 16, and i build the qt-1.7.0 with depth of
> 4,8,16,24,32, and meet two problems ,first it's the calibrate , when
> it start i didn't pass the calibrate or something we have to locate
> the touch mouse coordinate (so the we mouse coordinate is not
> correct)? but my qt-1.7.0 just pass through , can display the desktop
> of the qt,(it's ok as long as we can run the new qt on my device ),
> the second problems is .. when i run the cvm with the example of
> DemoXlet ,the whole screen become blank ,and graduately display the
> DemoXlet ,but when i touch the screen , it disappear. why ? i think
> this is not the qt depth problems any more.

This looks like the same bug that Rafael found. See this forum thread:

http://forums.java.net/jive/thread.jspa?messageID=212390#213495

Since this is a valid bug, we will need a volunteer from the developer
community to help fix it. I can give the details to someone willing to
help first debug then fix this bug.

Let me know if someone out there would like to volunteer to fix this bug.

Thanks,

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

Hi Hinkmond ,

Good news , the whole problems maybe cause for qt -qws ! I mean it's because i modefy the
QtBackEnd.cpp to support the -qws(actually mr1 isn't support ), but the point is ,if we run some explems which needs the support of cvmc or AMS, i think that maybe cause errors?
so if we run the cvmc first ,and then run the cvm, so i solve the errors i met before ,
but i don't know Rafael's is the same as me ???

and sorry for the misleading .Sorry!

Winson

Hinkmond Wong

phonemeadvanced@mobileandembedded.org wrote:
> Hi Hinkmond ,
>
> Good news , the whole problems maybe cause for qt -qws ! I mean it's because i modefy the
> QtBackEnd.cpp to support the -qws(actually mr1 isn't support ), but the point is ,if we run some explems which needs the support of cvmc or AMS, i think that maybe cause errors?
> so if we run the cvmc first ,and then run the cvm, so i solve the errors i met before ,
> but i don't know Rafael's is the same as me ???
>
> and sorry for the misleading .Sorry!
>
>

No problem. Glad to hear you worked out your problem.

Thanks,
Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

Hinkmond Wong

Hi Winson,

On the Zaurus (Linux/XScale/QtEmbedded device) we often see the same
error you report below if you log in as one user (such as
user="zaurus"), but the Qtopia window manager (launcher/QPE) is started
as a different user (such as root).

Check your /tmp directory to see if there are conflicting QPE socket
connect user files. They need to all match if you want the QWS Qtopia
manager (QPE) to talk with the Qt/Embedded clients you wish to launch.
They are dependent on your LOGNAME variable which is your userid when
you log in. If QPE was automatically started by root, you have to run
cvm as root

It should look like this in your /tmp dir:

drwx------ 2 root root 1024 Aug 19 21:40
/tmp/qtembedded-unknown

srw------- 1 root root 0 Aug 19 21:40
/tmp/qtembedded-unknown/QtEmbedded-0

Also, do a "ps -ef" in a shell on your device to make sure you the qpe
process was started as the same userid as you are when you log in and
try running cvm.

If not, log out, and log back in with the same userid as the qpe process.

Hinkmond

phonemeadvanced@mobileandembedded.org wrote:
> Hi , i am back .
>
>
>
> But i am still get the same problems , even i use the same version of qt(qt-2.3.7),
> ,the fellow problems still....
>
> .i set "export QTDIR=/mnt/qt-2.3.7 export LD_LIBRARY_PATH=mnt/qt-2.3.7/lib QWS_CLIENT=a " and then ./bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar
>
>
>> @@XletRunner starting Xlet basis.DemoXlet
>> QSocket
>> ::writeBlock: Socket is not open
>> QSocket
>> ::writeBlock: Socket is not open
>> QSocket
>> ::writeBlock: Socket is not open
>> QSocket
>> ::writeBlock: Socket is not open
>>
>> No Qt/Embedded server appears to be running.

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

yes, the QTE start it automatically as root when the system start it, so how can i run the cvm as the root?

the fellow is the context in the /tmp/

[root@OURSELEC tmp]# ls -l
-rw-r--r-- 1 root root 0 Jan 1 00:01 qcop-msg-qpe
-rw-r--r-- 1 root root 0 Jan 1 00:01 qcop-msg-quicklauncher
drwx------ 1 root root 0 Jan 1 00:06 qtembedded-root
drwx------ 1 root root 0 Jan 1 00:01 qtembedded-unknown

srw------- 1 root root 0 Jan 1 00:01 QtEmbedded-0

when i use the ps -A

[root@OURSELEC mnt]# ps -A
PID Uid VmSize Stat Command
1 root 548 S init
2 root SW [keventd]
3 root SWN [ksoftirqd_CPU0]
4 root SW [kswapd]
5 root SW [bdflush]
6 root SW [kupdated]
7 root SW [kUCB1x00d]
9 root SW [mtdblockd]
10 root SW [khubd]
12 root SW [krfcommd]
46 root SWN [jffs2_gcd_mtd2]
68 root SWN [jffs2_gcd_mtd3]
73 root SW [mmcblockd]
96 root 576 S syslogd -m 0
98 root 544 S klogd
108 rpc 636 S portmap
131 root 796 S xinetd -stayalive -reuse -pidfile
/var/run/xinetd.pid
154 root 1436 S -bash
155 root 1124 S /bin/sh -c exec /usr/qpe/qpe.sh &> /dev/null
180 root 10380 S ./qpe -qws
181 root SW [ktsd]
182 root 6860 S today
184 root SW [rpciod]
185 root SW [lockd]
228 root 5232 S N quicklauncher
242 root 668 R ps -A

what is your meaning of LOGNAME ? and how can i login and logout and control the usrid of some proccess?

by the way ,i am trying to make jpeglib for my qte, but i fail and meet with this

root@localhost jpeg]# make
./libtool --mode=compile /usr/local/arm-linux/arm-linux/bin/arm-linux-gcc -O2 -I. -c ./jcapimin.c
make: ./libtool: Command not found
make: *** [jcapimin.lo] Error 127

then i check the makefile and modify the

LIBTOOL = ./libtool
to
LIBTOOL = libtool

then i meet this

[root@localhost jpeg]# make
./libtool --mode=compile /usr/local/arm-linux/arm-linux/bin/arm-linux-gcc -O2 -I. -c ./jcapimin.c
make: ./libtool: Command not found
make: *** [jcapimin.lo] Error 127
[root@localhost jpeg]# make
libtool --mode=compile /usr/local/arm-linux/arm-linux/bin/arm-linux-gcc -O2 -I. -c ./jcapimin.c
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
make: *** [jcapimin.lo] Error 1

and problems also happened of compiling the e2fsprogs-1.35.tar.gz for my libuuid.so??

why i wanna do this is ,the qt library gave by the manufacturer only have few library , so i wanna to make the qt library myself, is the jpeg ,and e2fsprogs-1.35.tar.gz neccessary for this?

thanks so much!
winson

i am waiting online!!

Message was edited by: pigboy

Hinkmond Wong

Hi Winson,

When you type in your command line for CDC "cvm ...", how do you do
that? Do you log in using telnet and use a bash shell?

If you do, try this command line:

echo $LOGNAME

What does it say?

If it does not say "root" then there are problems. You should be able
to telnet to your device as root using the root password. If you
cannot, you should check with the manufacturer of the device or a device
user group forum on how you should do that.

By the way, what is the name of your device?

Hinkmond

phonemeadvanced@mobileandembedded.org wrote:
> yes, the QTE start it automatically as root when the system start it, so how can i run the cvm as the root?
>
> the fellow is the context in the /tmp/
>
> [root@OURSELEC tmp]# ls -l
> -rw-r--r-- 1 root root 0 Jan 1 00:01 qcop-msg-qpe
> -rw-r--r-- 1 root root 0 Jan 1 00:01 qcop-msg-quicklauncher
> drwx------ 1 root root 0 Jan 1 00:06 qtembedded-root
> drwx------ 1 root root 0 Jan 1 00:01 qtembedded-unknown
>
> srw------- 1 root root 0 Jan 1 00:01 QtEmbedded-0
>
> when i use the ps -A
>
> [root@OURSELEC mnt]# ps -A
> PID Uid VmSize Stat Command
> 1 root 548 S init
> 2 root SW [keventd]
> 3 root SWN [ksoftirqd_CPU0]
> 4 root SW [kswapd]
> 5 root SW [bdflush]
> 6 root SW [kupdated]
> 7 root SW [kUCB1x00d]
> 9 root SW [mtdblockd]
> 10 root SW [khubd]
> 12 root SW [krfcommd]
> 46 root SWN [jffs2_gcd_mtd2]
> 68 root SWN [jffs2_gcd_mtd3]
> 73 root SW [mmcblockd]
> 96 root 576 S syslogd -m 0
> 98 root 544 S klogd
> 108 rpc 636 S portmap
> 131 root 796 S xinetd -stayalive -reuse -pidfile
> /var/run/xinetd.pid
> 154 root 1436 S -bash
> 155 root 1124 S /bin/sh -c exec /usr/qpe/qpe.sh &> /dev/null
> 180 root 10380 S ./qpe -qws
> 181 root SW [ktsd]
> 182 root 6860 S today
> 184 root SW [rpciod]
> 185 root SW [lockd]
> 228 root 5232 S N quicklauncher
> 242 root 668 R ps -A
>
>
>
> what is your meaning of LOGNAME ? and how can i login and logout and control the usrid of some proccess?
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

Hi Hinkmond,
My device is Intel PXA270 EP.
Yes, i am using the telnet to login ,and logname is root.
So what can i do next ?
by the way ,what is the time difference of you and me , i really want to test it immediately when you talk me ,i don't wanna let this kinds of simple questions keep us waiting for 24 hours,last night ,i waited until the 3 o clock in the midnight ,i would really appreciate ! Thanks!

my command is like this:

./bin/cvm com.sun.xlet.XletRunner -name basis -path democlasses.jar

the cvm works if i use this:

./bin/cvm -cp testclasses.zip Test

today ,i typed

./bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar

i meet the fellow

@@XletRunner starting Xlet basis.DemoXlet
QServerSocket: failed to bind or listen to the socket
initXlet
startXlet
Can't drive depth 32

Winson

Message was edited by: pigboy

Message was edited by: pigboy

Hinkmond Wong

Hi Winson,

phonemeadvanced@mobileandembedded.org wrote:
> Hi Hinkmond,
> My device is Intel PXA270 EP.
>

That's the CPU. But, what is the company brand name and the model name
of your device? It would help to know what that is to understand your
runtime environment.

> Yes, i am using the telnet to login ,and logname is root.
> So what can i do next ?
>

Try copying your libqte.so and/or libqte-mt.so files directly from your
device over to your host system cross-compiler lib/ area where you build
your executable

For example:

First rename the old libqte.so to something else
mv /usr/lib/libqte.so
/usr/lib/libqte.so.sav

Then copy the libqte.so directly from your device into your
cross-compiler lib directory
cp /libqte.so /usr/lib/libqte.so

NOTE: The location of the lib directory maybe different for your
cross-compiler. Just find the cross-compiler version of libqte.so on
your host PC to see where you should copy your device libqte.so to.

Then do a "make clean" and rebuild your executable.

> by the way ,what is the time difference of you an
> d me , i really want to test it immediately when you talk me ,i don't wanna let this kinds of simple questions keep us waiting for 24 hours,last night ,i waited until the 3 o clock in the midnight ,i would really appreciate ! Thanks

I'm in the US/Pacific timezone. Sorry you had to wait, but this is free
support for our Open Source software, so you will get response from the
team only when there is spare time. If you want commercial support,
which you have to pay for but get faster response, you should contact
the following:

Java Partner Engineering:
http://www.sun.com/software/jpe/ls/index.xml
http://www.sun.com/software/jpe/contacts/

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

Hi Hinkmond ,

My device model is GX-PXA270-EP is a lab expriment . It's make by Beijing GenXin Company .
it preintall the qt vesion 2.

when i try to copy the libqte.so from my device ,i gave a Permission Denied . Maybe this is because i use the NFS ,but i set the authority of right to the folder i shared ? or the firewall , but i don;t have firewall install for my host pc.

Last , i am only a university studnet , i don't think i have the money to pay for the commercial fee of the suppot . but when i get a job , i think i will thind about it .

anyway ,i really thanks the free software suppot from you guys ,especial you and Jiangli Zhou .

Thanks!

Hinkmond Wong

phonemeadvanced@mobileandembedded.org wrote:
> Hi Hinkmond ,
>
> My device model is GX-PXA270-EP is a lab expriment . It's make by Beijing GenXin Company .
> it preintall the qt vesion 2.
>
> when i try to copy the libqte.so from my device ,i gave a Permission
> Denied . Maybe this is because i use the NFS ,but i set the authority of
> right to the folder i shared ? or the firewall , but i don;t have
> firewall install for my host pc.

I think the libqte.so that you built on your host system does not match
the libqte.so on your target system, probably because it does not have
Qtopia/QPE enabled.

When you built your Qt/Embedded do you remember if you built the
libqpe.so also?

If you did not, you should make sure to also download and build
libqpe.so so that you can cross-compile phoneME Advanced with QPE for
your device (which using Qtopia/QPE as seen in your ps -A output).

The best thing to do is to not download Qt/Embedded and QPE by yourself
independently, but to instead get the official Qt/Embedded/QPE SDK
directly from GenXin specifically for the GX-PXA270-EP device.

Otherwise, you may risk not matching exactly with the libqte.so and
libqpe.so on the device with your cross-compiler toolchain. If you
don't match, after you build phoneME Advanced using your cross-compiler
toolchain with the wrong libqte.so or libqpe.so you will see the errors
like you are currently seeing.

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

I am no double whether the libqte.so compatible or no , because the GeXin gave us CD(with cross compile tool ) ,when we put in the CD, just run the ./Install , it will automatically install the arm-linux- cross compile and qttoolchian(qte-2.3.7 ,qtopia1.7,x112.3.3,tmake1.1.1 ,tslib ).
when i build the cvm locate the QT_TARGET_DIR=.../qt-2.3.7(because is don't have the font folder so i copy the font folder from the qt-2.3.7 which i download from the website ),i can successed in making the pb cvm ,and but i run in my device , and meet the problems of

bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar
@@XletRunner starting Xlet basis.DemoXlet
QServerSocket: failed to bind or listen to the socket
initXlet
startXlet
Can't drive depth 32

so i want to compile the qt-2.3.7 as the depth of 16, but i alway meet the problems of the building the e2fsprog and jpeg :
[b]
the errors of e2fs .....[/b]

[i][b][root@localhost e2fs]# ./configure --host=arm-linux --enable-elf-shlibs --with-cc=arm-linux-cc --with-linker=arm-linux-ld -prefix=/usr/local/arm-linux/arm-linux/[/b][/i]

[[u][b]root@localhost e2fs]# make[/b][/u]
for i in lib/ext2fs/ext2_types.h lib/blkid/blkid_types.h lib/uuid/uuid_types.h ; do if test -d `dirname $i` ; then make $i ; fi ; done
make[1]: Entering directory `/arm-target/e2fs'
./util/subst -f ./util/subst.conf ./lib/ext2fs/ext2_types.h.in \
> lib/ext2fs/ext2_types.h
/bin/sh: ./util/subst: cannot execute binary file
make[1]: *** [lib/ext2fs/ext2_types.h] Error 126
make[1]: Leaving directory `/arm-target/e2fs'
make[1]: Entering directory `/arm-target/e2fs'
make[1]: `lib/blkid/blkid_types.h' is up to date.
make[1]: Leaving directory `/arm-target/e2fs'
make[1]: Entering directory `/arm-target/e2fs'
make[1]: `lib/uuid/uuid_types.h' is up to date.
make[1]: Leaving directory `/arm-target/e2fs'
make libs
make[1]: Entering directory `/arm-target/e2fs'
for i in lib/ext2fs/ext2_types.h lib/blkid/blkid_types.h lib/uuid/uuid_types.h ; do if test -d `dirname $i` ; then make $i ; fi ; done
make[2]: Entering directory `/arm-target/e2fs'
make[2]: `lib/ext2fs/ext2_types.h' is up to date.
make[2]: Leaving directory `/arm-target/e2fs'
make[2]: Entering directory `/arm-target/e2fs'
make[2]: `lib/blkid/blkid_types.h' is up to date.
make[2]: Leaving directory `/arm-target/e2fs'
make[2]: Entering directory `/arm-target/e2fs'
make[2]: `lib/uuid/uuid_types.h' is up to date.
make[2]: Leaving directory `/arm-target/e2fs'
for subdir in lib/et lib/ss lib/e2p lib/ext2fs lib/uuid lib/blkid intl; do \
if test -d $subdir ; then \
target=`echo all-libs-recursive|/bin/sed 's/-libs-recursive//'`; \
echo making $target in $subdir; \
(cd $subdir && make $target) || exit 1; \
fi ; \
done
making all in lib/et
make[2]: Entering directory `/arm-target/e2fs/lib/et'
../../util/subst -f ../../util/subst.conf ./compile_et.sh.in compile_et
../../util/subst: ../../util/subst: cannot execute binary file
make[2]: *** [compile_et] Error 126
make[2]: Leaving directory `/arm-target/e2fs/lib/et'
make[1]: *** [all-libs-recursive] Error 1
make[1]: Leaving directory `/arm-target/e2fs'
make: *** [all] Error 2

[b]the errors of jpeg...[/b]

[root@localhost jpeg]# make
./libtool --mode=compile gcc -O2 -I. -c ./jcapimin.c
make: ./libtool: Command not found
make: *** [jcapimin.lo] Error 127

Thanks!

Winson

Hinkmond Wong

phonemeadvanced@mobileandembedded.org wrote:
> I am no double whether the libqte.so compatible or no , because the GeXin gave us CD(with cross compile tool ) ,when we put in the CD, just run the ./Install , it will automatically install the arm-linux- cross compile and qttoolchian(qte-2.3.7 ,qtopia1.7,x112.3.3,tmake1.1.1 ,tslib ).
> when i build the cvm locate the QT_TARGET_DIR=.../qt-2.3.7(because is don't have the font folder so i copy the font folder from the qt-2.3.7 which i download from the website ),i can successed in making the pb cvm ,and but i run in my device , and meet the problems of
>
> bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar
> @@XletRunner starting Xlet basis.DemoXlet
> QServerSocket: failed to bind or listen to the socket
> initXlet
> startXlet
> Can't drive depth 32
>
> so i want to compile the qt-2.3.7 as the depth of 16, but i alway meet the problems of the building the e2fsprog and jpeg :
> [b]
> the errors of e2fs .....[/b]

Hi Winson,

You should contact GenXin and tell them they need to provide you with a
new libqte.so that is built to match their device which has a depth of 16.

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

jiangli_zhou
Offline
Joined: 2006-10-16

You need to start the first Qt application as the Qt/Embedded server. That means the first VM instance you launched can be the Qt/Embedded server. In the latest mr2 QtBachEnd.cpp, there's following code that pass '-qws' to QApplication based on the QWS_CLIENT environment variable setting:

char **
QtScreen::getArgs(int *argc) {
int count;
// Use the "-sync" flag to force Xlib calls to be synchronous, which
// would aid in debugging Xlib async errors.

static char *argv[] = {"cvm", "-qws", NULL};

count = 1;

#ifdef QWS
#ifndef QTOPIA
// If environment varible QWS_CLIENT is not defined,
// assume we are running as the server (in the qt-embedded sense).
if (getenv("QWS_CLIENT") == NULL) {
count++;
}
#endif /* QTOPIA */
#endif /* QWS */

*argc = count;

return (char **)&argv;
}

You can try to back port that to the mr1 copy that you have. After you rebuild CVM with the changes, when you launch the VM it'll be started as the Qt/Embedded server by default. If you want to run multiple VM instances at the same time, you can set QWS_CLIENT by doing "export QWS_CLIENT=" after you launched the first VM instance. The subsequently launched VM will not run as the Qt server.

Jiangli Zhou

pigboy
Offline
Joined: 2006-03-08

Hi , i am back .

But i am still get the same problems , even i use the same version of qt(qt-2.3.7),
,the fellow problems still....

.i set "export QTDIR=/mnt/qt-2.3.7 export LD_LIBRARY_PATH=mnt/qt-2.3.7/lib QWS_CLIENT=a " and then ./bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar
>

> @@XletRunner starting Xlet basis.DemoXlet
> QSocket
> ::writeBlock: Socket is not open
> QSocket
> ::writeBlock: Socket is not open
> QSocket
> ::writeBlock: Socket is not open
> QSocket
> ::writeBlock: Socket is not open
>
> No Qt/Embedded server appears to be running.

jiangli_zhou
Offline
Joined: 2006-10-16

Hi,

If you are using the patch I gave you, you should not set QWS_CLIENT=a when you start the first VM instance on the device. Because if QWS_CLIENT is set, it runs a client.

Make sure you don't set QWS_CLIENT to anything when you launching CVM.

Jiangli Zhou

pigboy
Offline
Joined: 2006-03-08

[u][b] Thanks for Jiangli and Hinkmond 's help , the cvm can work ..but i meet a new problems now ,

command line like ;
./bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar[/b][/u]

/mnt/lib/basis.jar" is not a valid classpath zip file or directory.

@@XletRunner starting Xlet basis.DemoXlet
QSocket
::writeBlock: Socket is not open
QSocket
::writeBlock: Socket is not open
QSocket
::writeBlock: Socket is not open
QSocket
::writeBlock: Socket is not open

No Qt/Embedded server appears to be running.

If you want to run cvm as a server,

add the "-qws" command-line option

and i try to add the -qws to the command option

but i shows cvm can;t recognize the "-qws" ?
or how can i sovle the Socket problem and the qt/embedded ??
Many thanks!

pigboy
Offline
Joined: 2006-03-08

i wanna ask
if we set CVM_PRELOAD_LID=true ,
after we made the cvm ,in the /lib we do have the class-lib.jar...

and when we execute the cvm, it wil show the error of "invalidate path......of /lib/class.lib.jar""

also ,if we don't set the CVM_PRELOAD_LID=true ...it always have problems ,why??

cjplummer
Offline
Joined: 2006-10-16

> i wanna ask
> if we set CVM_PRELOAD_LID=true ,
> after we made the cvm ,in the /lib we do have the
> class-lib.jar...
>
> and when we execute the cvm, it wil show the error of
> "invalidate path......of /lib/class.lib.jar""
>
I assume you mean cdc.jar or foundation.jar. This is normal for CVM_DEBUG=true CVM_PRELOAD_LIB=true builds. The file doesn't exist for CVM_PRELOAD_LIB=true builds, and CVM_DEBUG=true builds add a check and the message.

Chris

Hinkmond Wong

phonemeadvanced@mobileandembedded.org wrote:
> [b][u]thanks ,first, i check there is a libts.so in the qt-2.3.7/lib
> and i am checking the website you post to me ,thanks,
>

Try adding the libts.so to the link line in the Makefile when you try
building using qt-2.3.7

Change in build/share/defs_qt.mk from this line:
QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS)

To this line:
QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS) -lts

Then, "make clean" and rebuild.

Separately:

> and the below problems ,is the silly problems i have all the time....[/u]
> [/b]
>
> cc++ ../../build/linux-arm-xscale/./obj/QtBackEnd.o
> ../../src/share/basis/native/awt/qt/QtBackEnd.cpp:707:22: X11/Xlib.h: No such file or directory
> ../../src/share/basis/native/awt/qt/QtBackEnd.cpp: In function `QRgb*
> defaultColorTable(int*)':
> ../../src/share/basis/native/awt/qt/QtBackEnd.cpp:730: error: `Colormap'
> undeclared (first use this function)...
> make: *** [../../build/linux-arm-xscale/./obj/QtBackEnd.o] Error 1
>
> this is the error when i type in
> [b][u]
> make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true bin
> [/u][/b]
>

Try adding QT_EMBEDDED=true:
make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux-
QT_EMBEDDED=true \

QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true

> [u]and i build the qt-2.3.10 suggested by the blog of someone (sorry to forgot his name, but i didn't do the optional of his suggestion)
> http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatforms...
>
>
> the above error ,maybe shows i have to locate the X11 ,and i did that ,like type in ..[/u]
>
>
> make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true X11_LIB_DIR=/usr/X11R6/lib bin
>
> c ../../build/linux-arm-xscale/./obj/gifdecoder.o
> Linking ../../build/linux-arm-xscale/./lib/libqtawt_g.so
> /usr/local/arm-linux/lib/gcc-lib/arm-linux/3.3.2/../../../../arm-linux/bin/ld: cannot find -lqt-mt
> collect2: ld returned 1 exit status
> make: *** [../../build/linux-arm-xscale/./lib/libqtawt_g.so] Error 1
>
> i have the problems like this .
>

If you want to build QT_EMBEDDED=false (by default if not set), then the
library that the build tries to link is libqt-mt.so. However, in your
/usr/wins/qt-2.3.10/lib, you will probably find a libqte.so (Qt/Embedded
lib).

So, you want to make sure to set QT_EMBEDDED=true.

> or i used the qt-2.3.7 and x11-2.3.2(which were gave when i bought the device ,but i didn't build like the above link of the blog....because the company has done for me ,i think)
>

If you use the above, then you need to add the Touch Screen lib to the
Makefile link line:
Change in build/share/defs_qt.mk from this line:
QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS)

To this line:
QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS) -lts

> i think this is all the problems i have now , silly and tough???
>

The problem is trying too many types of Qt libs at once. Just pick
either qt-2.3.7 or qt-2.3.10. There are different ways to fix the
different problems you are seeing, but you need to choose which one you
want to solve.

qt-2.3.7: Add -lts to the link line
qt-2.3.10: Add QT_EMBEDDED=true to the make command

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

Hinkmond Wong

Hinkmond Wong wrote:
> phonemeadvanced@mobileandembedded.org wrote:
>> [b][u]thanks ,first, i check there is a libts.so in the qt-2.3.7/lib
>> and i am checking the website you post to me ,thanks,
>>

Sorry. Here's a correction from Jiangli (use this instead of below to
add the libts.so to your link line):

Change in build/share/defs_qt.mk from this line:
AWT_LIB_LIBS ?= $(QT_LIB_LIBS) -L$(QT_TARGET_LIB_DIR) -l$(QT_LIBRARY)
-lstdc++

To this line:
AWT_LIB_LIBS ?= $(QT_LIB_LIBS) -L$(QT_TARGET_LIB_DIR) -l$(QT_LIBRARY)
-lstdc++ -lts

Hinkmond

> Try adding the libts.so to the link line in the Makefile when you try
> building using qt-2.3.7
>
> Change in build/share/defs_qt.mk from this line:
> QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS)
>
> To this line:
> QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS) -lts
>
> Then, "make clean" and rebuild.
>
>
> Separately:
>
>> and the below problems ,is the silly problems i have all the
>> time....[/u]
>> [/b]
>>
>> cc++ ../../build/linux-arm-xscale/./obj/QtBackEnd.o
>> ../../src/share/basis/native/awt/qt/QtBackEnd.cpp:707:22: X11/Xlib.h:
>> No such file or directory
>> ../../src/share/basis/native/awt/qt/QtBackEnd.cpp: In function `QRgb*
>> defaultColorTable(int*)':
>> ../../src/share/basis/native/awt/qt/QtBackEnd.cpp:730: error: `Colormap'
>> undeclared (first use this function)...
>> make: *** [../../build/linux-arm-xscale/./obj/QtBackEnd.o] Error 1
>>
>> this is the error when i type in [b][u]
>> make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux-
>> QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true bin
>> [/u][/b]
>>
>
> Try adding QT_EMBEDDED=true:
> make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux-
> QT_EMBEDDED=true \
>
> QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true
>
>
>> [u]and i build the qt-2.3.10 suggested by the blog of someone (sorry
>> to forgot his name, but i didn't do the optional of his suggestion)
>> http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatforms...
>>
>>
>>
>> the above error ,maybe shows i have to locate the X11 ,and i did that
>> ,like type in ..[/u]
>>
>>
>> make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux-
>> QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true
>> X11_LIB_DIR=/usr/X11R6/lib bin
>>
>> c ../../build/linux-arm-xscale/./obj/gifdecoder.o
>> Linking ../../build/linux-arm-xscale/./lib/libqtawt_g.so
>> /usr/local/arm-linux/lib/gcc-lib/arm-linux/3.3.2/../../../../arm-linux/bin/ld:
>> cannot find -lqt-mt
>> collect2: ld returned 1 exit status
>> make: *** [../../build/linux-arm-xscale/./lib/libqtawt_g.so] Error 1
>>
>> i have the problems like this .
>>
>
> If you want to build QT_EMBEDDED=false (by default if not set), then
> the library that the build tries to link is libqt-mt.so. However, in
> your /usr/wins/qt-2.3.10/lib, you will probably find a libqte.so
> (Qt/Embedded lib).
> So, you want to make sure to set QT_EMBEDDED=true.
>
>> or i used the qt-2.3.7 and x11-2.3.2(which were gave when i bought
>> the device ,but i didn't build like the above link of the
>> blog....because the company has done for me ,i think)
>
> If you use the above, then you need to add the Touch Screen lib to the
> Makefile link line:
> Change in build/share/defs_qt.mk from this line:
> QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS)
>
> To this line:
> QT_LIB_LIBS ?= -lstdc++ $(X11_LIBS) -lts
>
>> i think this is all the problems i have now , silly and tough???
>>
>
> The problem is trying too many types of Qt libs at once. Just pick
> either qt-2.3.7 or qt-2.3.10. There are different ways to fix the
> different problems you are seeing, but you need to choose which one
> you want to solve.
>
> qt-2.3.7: Add -lts to the link line
> qt-2.3.10: Add QT_EMBEDDED=true to the make command
>
> Hinkmond
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

Hi, Hinkmond

[u]AWT_LIB_LIBS ?= $(QT_LIB_LIBS) -L$(QT_TARGET_LIB_DIR) -l$(QT_LIBRARY)
-lstdc++ -lts[/u]

is the (QT_LIBRARY) should be QT_LIB ???

i did modify the qt_defs_mk.like you suggested, and it doesn't work, if i type it

[b] [u]make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux-
> QT_EMBEDDED=true \
>
> QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true[/u][/b]

but it successed if i type in the command line you gave it to me last time

[b][u]make CVM_TERSEOUTPUT=false J2ME_CLASSLIB=basis QTEMBEDDED=true
QTOPIA=false CVM_TARGET_TOOLS_PREFIX=arm-linux-
CVM_PRELOAD_LIB=true QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true bin[/u][/b]

i don't have device to test it until monday morning , and i hope this time works.

Many thanks! Really!
Winson

cjplummer
Offline
Joined: 2006-10-16

Please see the following:

http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedCVMNative...

Most likely QT in not in your LD_LIBRARY_PATH. You can fix this in your shell by adding your QT lib direcotry to the LD_LIBRARY_PATH variable. If you build CDC with CVM_DEBUG=true, this should help you figure out if this is actually the problem or not.

Chris

pigboy
Offline
Joined: 2006-03-08

Thanks ,Hinkmond and Chris, sorry to replay late, i am busying with my m3g programme design as my graduate thesis.but i will try this and let you know ,
thanks so much !
and another question , i try to reintsll a Qt ,including qt-embedded -2.3.7, and qt/x11-2.3.3, and and whole qt(which was package by the company which i bought the target device ) , but i fail with diffirent kinds of problems , like the compiler C or something, it's that happened so ?
Thanks!

Hinkmond Wong

Hi Winson,

phonemeadvanced@mobileandembedded.org wrote:
> Thanks ,Hinkmond and Chris, sorry to replay late, i am busying with my m3g programme design as my graduate thesis.but i will try this and let you know ,
> thanks so much !
> and another question , i try to reintsll a Qt ,including qt-embedded -2.3.7, and qt/x11-2.3.3, and and whole qt(which was package by the company which i bought the target device ) , but i fail with diffirent kinds of problems , like the compiler C or something, it's that happened so ?
>

What is the name of the company that makes your target device? Do they
have a URL to download their version of Qt found on their device? It
would be good for us to try to mimic what your environment is like to
answer your questions.

Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

Intel PXA270 /Intel OURS PXA 270 EP ,and i have the Qt and install it ,which the croass compiler (arm-linux) provide the toolchain ,(qt-embedded2.3.7) ,

make CVM_TERSEOUTPUT=false QTEMBEDDED=true QTOPIA=false CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/local/arm-linux/qt_toolchain/qt-2.3.7 J2ME_CLASSLIB=basis CVM_PRELOAD_LIB=true CVM_DEBUG=true bin

./../build/linux-arm-xscale/./obj/jdmainct.o ../../build/linux-arm-xscale/./obj/jfdctflt.o ../../build/linux-arm-xscale/./obj/jcinit.o ../../build/linux-arm-xscale/./obj/jctrans.o ../../build/linux-arm-xscale/./obj/jdmarker.o ../../build/linux-arm-xscale/./obj/jfdctfst.o ../../build/linux-arm-xscale/./obj/jquant1.o ../../build/linux-arm-xscale/./obj/jcmainct.o ../../build/linux-arm-xscale/./obj/jdapimin.o ../../build/linux-arm-xscale/./obj/jdmaster.o ../../build/linux-arm-xscale/./obj/jfdctint.o ../../build/linux-arm-xscale/./obj/jquant2.o ../../build/linux-arm-xscale/./obj/jcmarker.o ../../build/linux-arm-xscale/./obj/jdapistd.o ../../build/linux-arm-xscale/./obj/jdmerge.o ../../build/linux-arm-xscale/./obj/jidctflt.o ../../build/linux-arm-xscale/./obj/jutils.o ../../build/linux-arm-xscale/./obj/libromjava.a ../../build/linux-arm-xscale/./obj/fdlibm.a -lpthread -ldl -L/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib -lqte -lstdc++ -lm -lm
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_close'
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_config'
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_read'
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_open'
collect2: ld returned 1 exit status
make: *** [../../build/linux-arm-xscale/./bin/cvm] Error 1
this is the problem i have now ....

Hinkmond Wong

Hi Winson,

Looks like your Qt lib has a problem with the touchscreen library which
it cannot find during linking. I think you might have built your Qt
library without linking to the needed libts.so from your device.

Or, maybe these links will help you if you read Chinese:
http://www.qtcn.org/bbs/simple/index.php?t5628.html
http://www.qtcn.org/bbs/read.php?tid=3732&fpage=19

Or, in English:
http://www.qtforum.org/article/14098/qt-and-tslibhowto.html

I would suggest to look to see if you have libts.so in:
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib

If you don't, try to copy the libts.so file from somewhere off your
device to:
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib

and then try building again.

Also, try a "make clean" first.

Hinkmond

phonemeadvanced@mobileandembedded.org wrote:
> Intel PXA270 /Intel OURS PXA 270 EP ,and i have the Qt and install it ,which the croass compiler (arm-linux) provide the toolchain ,(qt-embedded2.3.7) ,
>
> make CVM_TERSEOUTPUT=false QTEMBEDDED=true QTOPIA=false CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/local/arm-linux/qt_toolchain/qt-2.3.7 J2ME_CLASSLIB=basis CVM_PRELOAD_LIB=true CVM_DEBUG=true bin
>
>
>
> ./../build/linux-arm-xscale/./obj/jdmainct.o ../../build/linux-arm-xscale/./obj/jfdctflt.o ../../build/linux-arm-xscale/./obj/jcinit.o ../../build/linux-arm-xscale/./obj/jctrans.o ../../build/linux-arm-xscale/./obj/jdmarker.o ../../build/linux-arm-xscale/./obj/jfdctfst.o ../../build/linux-arm-xscale/./obj/jquant1.o ../../build/linux-arm-xscale/./obj/jcmainct.o ../../build/linux-arm-xscale/./obj/jdapimin.o ../../build/linux-arm-xscale/./obj/jdmaster.o ../../build/linux-arm-xscale/./obj/jfdctint.o ../../build/linux-arm-xscale/./obj/jquant2.o ../../build/linux-arm-xscale/./obj/jcmarker.o ../../build/linux-arm-xscale/./obj/jdapistd.o ../../build/linux-arm-xscale/./obj/jdmerge.o ../../build/linux-arm-xscale/./obj/jidctflt.o ../../build/linux-arm-xscale/./obj/jutils.o ../../build/linux-arm-xscale/./obj/libromjava.a ../../build/linux-arm-xscale/./obj/fdlibm.a -lpthread -ldl -L/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib -lqte -lstdc++ -lm -lm
> /usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_close'
> /usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_config'
> /usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_read'
> /usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_open'
> collect2: ld returned 1 exit status
> make: *** [../../build/linux-arm-xscale/./bin/cvm] Error 1
> this is the problem i have now ....
> [Message sent by forum member 'pigboy' (pigboy)]
>
> http://forums.java.net/jive/thread.jspa?messageID=213082
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
> For additional commands, e-mail: advanced-help@phoneme.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

[b][u]thanks ,first, i check there is a libts.so in the qt-2.3.7/lib
and i am checking the website you post to me ,thanks,
and the below problems ,is the silly problems i have all the time....[/u]
[/b]

cc++ ../../build/linux-arm-xscale/./obj/QtBackEnd.o
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:707:22: X11/Xlib.h: No such file or directory
../../src/share/basis/native/awt/qt/QtBackEnd.cpp: In function `QRgb*
defaultColorTable(int*)':
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:730: error: `Colormap'
undeclared (first use this function)
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:730: error: (Each undeclared
identifier is reported only once for each function it appears in.)
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:730: error: parse error
before `=' token
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:732: error: `XColor'
undeclared (first use this function)
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:732: error: `carr' undeclared
(first use this function)
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:732: error: parse error
before `[' token
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:737: error: `cmap' undeclared
(first use this function)
../../src/share/basis/native/awt/qt/QtBackEnd.cpp:737: error: `XQueryColors'
undeclared (first use this function)
make: *** [../../build/linux-arm-xscale/./obj/QtBackEnd.o] Error 1

this is the error when i type in
[b][u]
make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true bin
[/u][/b]

[u]and i build the qt-2.3.10 suggested by the blog of someone (sorry to forgot his name, but i didn't do the optional of his suggestion)
http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatforms...

the above error ,maybe shows i have to locate the X11 ,and i did that ,like type in ..[/u]

make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true X11_LIB_DIR=/usr/X11R6/lib bin

c ../../build/linux-arm-xscale/./obj/gifdecoder.o
Linking ../../build/linux-arm-xscale/./lib/libqtawt_g.so
/usr/local/arm-linux/lib/gcc-lib/arm-linux/3.3.2/../../../../arm-linux/bin/ld: cannot find -lqt-mt
collect2: ld returned 1 exit status
make: *** [../../build/linux-arm-xscale/./lib/libqtawt_g.so] Error 1

i have the problems like this .

or i used the qt-2.3.7 and x11-2.3.2(which were gave when i bought the device ,but i didn't build like the above link of the blog....because the company has done for me ,i think)

make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/wins/qt-2.3.10 CVM_DEBUG=true X11_LIB_DIR=/usr/local/arm-linux/qt_toolchain/qt-2-3.2

it has the some problems like the ""make: *** [../../build/linux-arm-xscale/./obj/QtBackEnd.o] Error 1

make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/local/arm-linux/qt_toolchain/qt-2.3.7 CVM_DEBUG=true X11_LIB_DIR=/usr/local/arm-linux/qt_toolchain/qt-2.3.2 bin
[u]
[b]also have the problems ...make: *** [../../build/linux-arm-xscale/./obj/QtBackEnd.o] Error 1[/b][/u]

[u]make J2ME_CLASSLIB=basis CVM_TARGET_TOOLS_PREFIX=arm-linux- QT_TARGET_DIR=/usr/local/arm-linux/qt_toolchain/qt-2.3.7 CVM_DEBUG=true CVM_TERSEOUTPUT=false QTEMBEDDED=true QTOPIA=false CVM_PRELOAD_LIB=true bin which fellow you suggestion
[/u]

e/./obj/libromjava.a ../../build/linux-arm-xscale/./obj/fdlibm.a -lpthread -ldl -L/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib -lqte -lstdc++ -lm -lm
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_close'
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_config'
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_read'
/usr/local/arm-linux/qt_toolchain/qt-2.3.7/lib/libqte.so: undefined reference to `ts_open'
collect2: ld returned 1 exit status
make: *** [../../build/linux-arm-xscale/./bin/cvm] Error 1

this above problems is i alway suffering ....

i try to get rid of this ,by setting AWT_LIB_LIBS= (NONE)

i can success in making the cvm ,but when i run on my device ,it will throw the unsatisfiedLinkError...

i think this is all the problems i have now , silly and tough???

or can you give me you MSN ,then i can transfer my PXA 270
cdrom to you ,and you can modify and prove whether i did something wrong ,or something?

thanks!
winson

Message was edited by: pigboy

jiangli_zhou
Offline
Joined: 2006-10-16

Hi Winson,

Why does it need X11/Xlib.h? If you look at QtBackEnd.cpp, it only
includes X11/Xlib.h if Q_WS_X11 is #defined. I grep'd for Q_WS_X11 in
the source, and I don't see anywhere Q_WS_X11 is defined for basis. Is
it possible your modifications enabled Q_WS_X11 accidentally?

Your build command looks fine.

Jiangli Zhou

Hinkmond Wong

Hi Winson,

One possible solution is to make sure to transfer both the bin/ and lib/
directories to your device after you build, and also make sure to keep
them in the same directory on the same level.

The cvm binary tries too look for libqtawt.so in a relative path to "lib"

../lib/libqtawt.so

If it doesn't find the libqtawt.so file there, it will fail with the
UnsatisfiedLinkError.

Do you see the libqtawt.so file in your build/*/lib directory when you
build? If so, just make sure you transfer everything if both bin and
lib to your device into the same directory before testing.

If that file exists on your device, you need to send more info. Try
doing a CVM_DEBUG=true build and run again, copying and pasting the
output with the exact symbol that may be missing.

Hinkmond

phonemeadvanced@mobileandembedded.org wrote:
> i compiled the cvm by type
> make CVM_TARGET_TOOLS_PREFIX= arm-linux - QT_TARGET_DIR=/usr/lib/qt-2.3.10 X11_DIR_LIB=/usr/X11R6/lib AWT_LIB_LIBS= J2ME_CLASSLIB=basis bin
>
> i can successed in make the cvm,
> ./bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -path democlasses.jar
>
> but when i run i my target device , it throws out the [u]UnsatisfiedLinkError!!![/u]
> of libqtawt.so........
>
> i check the cvm_runtime_guaid ,and know maybe it says i have to locate the Qt path or something , the running the personal profile or personal basis profile ...
>
> can some one tell me how to do that , and what is the use of the lib_library_path ,,
>
> Thanks!!!
> [Message sent by forum member 'pigboy' (pigboy)]
>
> http://forums.java.net/jive/thread.jspa?messageID=211617
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
> For additional commands, e-mail: advanced-help@phoneme.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

Yes, the libqtawt.so is in the /lib ,and all the files generated when compiles the cvm (when we use the make .....bin ,it means the it will produces a tar.gz..package,so everything is inside ).

i can test the device today ,but i will send it tomorrow .thanks!

about the question, everytime when want to run the java class which require the AWT , it will throws the problems like that , and i also can't success in making personal profile cvm? it's this kinds of problems happened to you when you begin to do this , please help me , if i can make it ,i can go any further, the feeling is hard of stacked by it .Thanks!

Hinkmond Wong

phonemeadvanced@mobileandembedded.org wrote:
> Yes, the libqtawt.so is in the /lib ,and all the files generated when
> compiles the cvm (when we use the make .....bin ,it means the it will
> produces a tar.gz..package,so everything is inside ).
>
> i can test the device today ,but i will send it tomorrow .thanks!

OK. It will be important to use the CVM_DEBUG=true build so that you
can capture the output and find the missing symbol that the cvm says is
an UnsatifiedLink and cannot find. It's probably a Qt function that is
missing and it will be important to find out which exact one the error
is saying that is missing.

> about the question, everytime when want to run the java class which
> require the AWT , it will throws the problems like that , and i also
> can't success in making personal profile cvm? it's this kinds of
> problems happened to you when you begin to do this , please help me , if
> i can make it ,i can go any further, the feeling is hard of stacked by
> it .Thanks!

I've been using both phoneME Advanced PBP and PP builds (which both use
AWT) from the phoneME Advanced repository without problems, so it is
just a matter of figuring out the correct process for cross-compiling to
your specific device.

Which device are you using again? I forgot if you mentioned what device
it is that you are trying to port to. I know that using an HP iPAQ
(Windows Mobile 5.0) has no problems and of course a Linux/x86 PC
(reference platform) has no problems with pMEA PBP.

Also, you should make sure to test first on Linux/x86 to make sure
everything is working OK on the reference Linux/x86 PC version of
phoneME Advanced PBP before trying to debug your device. Eliminating
your variables is a good approach to getting your port working as fast
as possible. And, the way to do that is to start with a known good
state (like a Linux/x86 build that you know works) before incrementally
trying to get it running the same way on your device.

Hinkmond

> [Message sent by forum member 'pigboy' (pigboy)]
>
> http://forums.java.net/jive/thread.jspa?messageID=211764
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
> For additional commands, e-mail: advanced-help@phoneme.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

pigboy
Offline
Joined: 2006-03-08

First , i still have to say sorry ,i can't go to the lab today , so still can post the output ,it's pity , because i am doing my programming design (a jsr184 game design ) as my thesis, and working hard on it .i am really will send it tomorrow .

Second , my target device is Intel PXA270 /OURS=PXA270 EP, arm xscale, so it's a linux/arm ,no linux/x86, which you suggest my to test in it before porting to my device,.

Yes, i am sure it's the problems of Qt, but i can't find it out , anyway ,maybe tomorrow . i hope we can get this done,good luck!
and thanks!

i hurry to the lab this afternoon ,and get the error report , and hope you can help me figure out what the problems...
[u]
this is the error happened when i compiling the makefile
(i think this maybe give you the clue of the problems[/u]

c++
../../build/linux-arm-xscale/./obj/QtSync.o
c++
../../build/linux-arm-xscale/./obj/QtORB.o
/usr/lib/qt-2.3.1/include/qptrdict.h:
In member function `void

QPtrDict::deleteItem(void*) [with type = void]':

/usr/lib/qt-2.3.1/include/qptrdict.h:51: instantiated from here

/usr/lib/qt-2.3.1/include/qptrdict.h:82: warning: deleting `void*' is
undefined

c++ ../../build/linux-arm-xscale/./obj/QpObject.o

c++ ../../build/linux-arm-xscale/./obj/QtFontMetrics.o

c++ ../../build/linux-arm-xscale/./obj/QtGraphics.o

c++ ../../build/linux-arm-xscale/./obj/QtGraphicsConfiguration.o

c++ ../../build/linux-arm-xscale/./obj/QtGraphicsDevice.o

c++ ../../build/linux-arm-xscale/./obj/QtGraphicsEnv.o

c++ ../../build/linux-arm-xscale/./obj/QtImage.o

c++ ../../build/linux-arm-xscale/./obj/QtRobotHelper.o

c++ ../../build/linux-arm-xscale/./obj/QtToolkit.o

c++ ../../build/linux-arm-xscale/./obj/Window.o

c++ ../../build/linux-arm-xscale/./obj/QtBackEnd.o

c++ ../../build/linux-arm-xscale/./obj/QtApplication.o

/usr/lib/qt-2.3.1/include/qptrdict.h: In member function `void

QPtrDict::deleteItem(void*) [with type = void]':

/usr/lib/qt-2.3.1/include/qvaluelist.h:49: instantiated from here

/usr/lib/qt-2.3.1/include/qptrdict.h:82: warning: deleting `void*' is undefined

c++ ../../build/linux-arm-xscale/./obj/QtSync.o

c++ ../../build/linux-arm-xscale/./obj/QtORB.o

/usr/lib/qt-2.3.1/include/qptrdict.h: In member function `void

QPtrDict::deleteItem(void*) [with type = void]':

/usr/lib/qt-2.3.1/include/qptrdict.h:51: instantiated from here

/usr/lib/qt-2.3.1/include/qptrdict.h:82: warning: deleting `void*' is
undefined

c++ ../../build/linux-arm-xscale/./obj/QpObject.o

c++ ../../build/linux-arm-xscale/./obj/QpRobot.o

c++ ../../build/linux-arm-xscale/./obj/QtScreenFactory.o

[u][b]and this the results when i set cvm_debug=true flags and test the cvm on my target device[/b][/u]

./bin/cvm com.sun.xlet.XletRunner -name basis.DemoXlet -pat
CVM Configuration:

Java stack chunk size (stackChunkSize): 2048

Java stack minimum size (stackMinSize): 3072

Java stack maximum size (stackMaxSize): 131072
GC[SS]:
Initialized semi-space gen for generational GC

Size of *each* semispace in bytes=1048576

Limits of generation = [0x401bb200,0x403bb200)

First semispace = [0x401bb200,0x402bb200)

Second semispace = [0x402bb200,0x403bb200)
GC[MC]:
Initialized mark-compact gen for generational GC

Size of the space in bytes=4194304

Limits of generation = [0x403bb200,0x407bb200)
GC[generational]:
Auxiliary data structures

heapBaseMemoryArea=[0x401bb008,0x407bb208)

cardTable=[0x47ec90,0x481c90)

objectHeaderTable=[0x481c98,0x484c98)

summaryTable=[0x484ca0,0x490ca0)
JIT Configuration:

Interpreter transition cost (icost): 20

Mixed transition cost (mcost): 50

Backwards branch cost (bcost): 4

Compilation threshold (climit): 20000

When to compile (compile): policy

What to inline (inline): virtual+nonvirtual+vhints+ihints

Max Inlining Depth (maxInliningDepth): 12

Max Inlining Code Length (maxInliningCodeLength): 68

Min Inlining Code Length (minInliningCodeLength): 16

Policy Triggered Decompilations (policyTriggeredDecompilations): true

Max Working Memory Size (maxWorkingMemorySize): 563200

Max Compiled Method Size (maxCompiledMethodSize): 65535

Code Cache Size (codeCacheSize): 524288

Upper Code Cache Threshold (upperCodeCacheThreshold): 95%

Lower Code Cache Threshold (lowerCodeCacheThreshold): 90%

Pass Phi values in registers (XregisterPhis): true

Pass locals in registers between blocks (XregisterLocals): true

Compiling Causes Class Loading (XcompilingCausesClassLoading): false

Trace (trace): none

@@XletRunner starting Xlet basis.DemoXlet

/mnt/pb/lib/libqtawt_g.so: undefined symbol: _ZN7QString8fromUtf8EPKci

java.lang.UnsatisfiedLinkError: /mnt/pb/lib/libqtawt_g.so
at

java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/String;)V(Native)

at java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/lang/Strin)

at java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/File;Z))

at java.lang.ClassLoader.loadLibraryInternal(Ljava/lang/Class;Ljava/lan)

at java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/String)

at java.lang.Runtime.loadLibrary0(Ljava/lang/Class;Ljava/lang/String;)V)

at java.lang.System.loadLibrary(Ljava/lang/String;)V(System.java:885)

at
sun.security.action.LoadLibraryAction.run()Ljava/lang/Object;(LoadLi)

at java.security.AccessController.doPrivileged(Ljava/security/Privilege)

at java.security.AccessController.doPrivileged(Ljava/security/Privilege)

at java.awt.QtGraphicsEnvironment.()V(QtGraphicsEnvironment.java:)

at java.awt.QtToolkit.()V(QtToolkit.java:39)

at
java.lang.reflect.Constructor.newInstance([Ljava/lang/Object;)Ljava/)

at java.lang.Class.newInstance()Ljava/lang/Object;(Class.java:281)

at java.awt.Toolkit$1.run()Ljava/lang/Object;(Toolkit.java:183)

at
java.security.AccessController.doPrivileged(Ljava/security/Privilege)

at java.security.AccessController.doPrivileged(Ljava/security/Privilege)

at java.awt.Toolkit.getDefaultToolkit()Ljava/awt/Toolkit;(Toolkit.java:)

at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment()Ljava/awt/)

at java.awt.Window.(Ljava/awt/GraphicsConfiguration;)V(Window.jav)

at java.awt.Frame.(Ljava/lang/String;Ljava/awt/GraphicsConfigurat)

at java.awt.Frame.(Ljava/lang/String;)V(Frame.java:316)

at
com.sun.xlet.ToplevelFrame.(Ljava/lang/String;Lcom/sun/xlet/Xl)

at com.sun.xlet.XletManager.(Lcom/sun/xlet/XletClassLoader;Ljava/)

at com.sun.xlet.XletManager.createXlet(Ljava/lang/String;[Ljava/lang/St)

at com.sun.xlet.XletRunner.main([Ljava/lang/String;)V(XletRunner.java:1)

at java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object)

at sun.misc.CVM.runMain()V(CVM.java:478)

Message was edited by: pigboy

Message was edited by: pigboy

pigboy
Offline
Joined: 2006-03-08

Hi, Hinkmond ,
can you give the or discrible the process of the make the cvm ,or command line ?
i thought i really suffering for this month, thanks!

Hinkmond Wong

phonemeadvanced@mobileandembedded.org wrote:
> Hi, Hinkmond ,
> can you give the or discrible the process of the make the cvm ,or command line ?
> i thought i really suffering for this month, thanks!
>

Try this:

cd linux-arm-generic

make CVM_TERSEOUTPUT=false J2ME_CLASSLIB=basis QTEMBEDDED=true
QTOPIA=false \
CC= \
CCC= \
HOST_CC=/usr/bin/cc \
HOST_CCC=/usr/bin/g++ \
LEX=/usr/bin/flex \
BISON=/usr/bin/bison \
USE_GCC2=false \
QT_TARGET_DIR=/qt-2.3.10 \
CVM_PRELOAD_LIB=true

Hinkmond

> [Message sent by forum member 'pigboy' (pigboy)]
>
> http://forums.java.net/jive/thread.jspa?messageID=212256
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
> For additional commands, e-mail: advanced-help@phoneme.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

cjplummer
Offline
Joined: 2006-10-16

>
> cd linux-arm-generic
>
> make CVM_TERSEOUTPUT=false J2ME_CLASSLIB=basis
> QTEMBEDDED=true
> QTOPIA=false \
> CC= \
> CCC= \
Please don't! CC and CCC are not supported build options. Using CVM_TARGET_TOOLS_PREFIX is best. The second best choice is to set all the TARGET_XXX options seperately.

> HOST_CC=/usr/bin/cc \
> HOST_CCC=/usr/bin/g++ \
> LEX=/usr/bin/flex \
> BISON=/usr/bin/bison \
> USE_GCC2=false \
None of the above should be needed.

Chris

> QT_TARGET_DIR=/qt
> -2.3.10 \
> CVM_PRELOAD_LIB=true
>
>
> Hinkmond
>
> > [Message sent by forum member 'pigboy' (pigboy)]
> >
> >
> http://forums.java.net/jive/thread.jspa?messageID=2122
> 56
> >
> >
> ------------------------------------------------------
> ---------------
> > To unsubscribe, e-mail:
> advanced-unsubscribe@phoneme.dev.java.net
> > For additional commands, e-mail:
> advanced-help@phoneme.dev.java.net
> >
> >
>
> ------------------------------------------------------
> ---------------
> To unsubscribe, e-mail:
> advanced-unsubscribe@phoneme.dev.java.net
> For additional commands, e-mail:
> advanced-help@phoneme.dev.java.net

Hinkmond Wong

Sorry, Winson. Chris is right. (I listed a very old and bad way of
doing a cross-target device build) Try this instead (follows Chris's
suggestion):

make CVM_TERSEOUTPUT=false \
J2ME_CLASSLIB=basis \
QTEMBEDDED=true \
QTOPIA=false \
CVM_TARGET_TOOLS_PREFIX= \
QT_TARGET_DIR= \
CVM_PRELOAD_LIB=true

Hinkmond

phonemeadvanced@mobileandembedded.org wrote:
>> cd linux-arm-generic
>>
>> make CVM_TERSEOUTPUT=false J2ME_CLASSLIB=basis
>> QTEMBEDDED=true
>> QTOPIA=false \
>> CC= \
>> CCC= \
>>
> Please don't! CC and CCC are not supported build options. Using CVM_TARGET_TOOLS_PREFIX is best. The second best choice is to set all the TARGET_XXX options seperately.
>
>
>> HOST_CC=/usr/bin/cc \
>> HOST_CCC=/usr/bin/g++ \
>> LEX=/usr/bin/flex \
>> BISON=/usr/bin/bison \
>> USE_GCC2=false \
>>
> None of the above should be needed.
>
> Chris
>
>
>> QT_TARGET_DIR=/qt
>> -2.3.10 \
>> CVM_PRELOAD_LIB=true
>>
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net