PDA

View Full Version : porting minicom

mbertazz
08-29-2006, 01:33 PM
hi,
i'm trying to port an application to nokia 770.
I downloaded application SRC tar.gz:
http://alioth.debian.org/download.php/1721/minicom-2.2-rc2.tar.gz

gunzipped it in sbox and:
./configure --host=arm-maemo-elf --PREFIS=/home/MYUSER/maemo-minicom-0.0.1 OK
./make OK
./make install OK

Now, if i use minicom exe on my nokia 770 (os 2006) as root, after chmod + x, with this command:

/tmp # ./minicom

this is the output:
/bin/sh: ./minicom: not found

Same with another app (serproxy), so where is the problem?

thank youin advance,
mbertazz
MikeL
08-29-2006, 02:41 PM
What happens if you omit the ./ as running Hamachi on the Nokia 770 I needed to omit the ./ when running the various program routines/options etc.

PS not hot on linux generally so could be completely off the mark :o
mbertazz
08-29-2006, 08:46 PM
hi,
always the same message, both with absolute path and without ./

other ideas?

thanks
aleksandyr
08-29-2006, 11:49 PM
Please post your target configuration details. (compiler, build kit, etc.)
aflegg
08-30-2006, 04:20 AM
It sounds like the executable archiecture isn't ARMEL.

You're building it in Scratchbox, yes?
ziobudda
02-12-2007, 04:25 PM
i have the same error with a personal application written with FreePascal and compiled using arm-crosscompiling ... i think there are two possibilities:
1) the binary isn't an ARMEL (try from your linux box -> file minicom and read the report)
2) the binary is an ARMEL but is linked with errors/mistakes library....

at this time i don't found a solution yet...:confused:
TA-t3
02-13-2007, 06:10 AM
It must be the wrong architecture. If it was the right one, but missing libs it would have given a different type of error.
spycedtx
02-28-2007, 08:19 PM
It must be the wrong architecture. If it was the right one, but missing libs it would have given a different type of error.

Not necessarily, as I so found while trying to get phonelink running. I took the armel app, put it back on my PC so I could run strings on it. It was trying to access some libs that didn't exist on my tablet. Even ldd was giving the "not found" errors. Once I located the missing lib(s), it moved on to other issues. :)

or, so was my experience.