[maemo-developers] [maemo-developers] Help, executable file dosen't execute.
From: smartkenny smartkenny at gmail.comDate: Tue Jun 13 21:58:30 EEST 2006
- Previous message: [maemo-developers] Help, executable file dosen't execute.
- Next message: [maemo-developers] Help, executable file dosen't execute.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, Eero and Andrew, I contacted with Daniël who is a FPC developer, and he want to ask the following questions: Can you ask them what the different between EABI and normal cdecl calling convention is? Obviously, since GTK is C code, all interfacing to it is expected to have cdecl calling convention. We support for ARM: - Cdecl - CPPcdecl - same as cdecl but with different name mangling - Stdcall - Stdcall with floating point numbers handled like equal integers (called softfloat by us). Greetings, Daniël Eero Tamminen wrote: > Hi, > > On Tue, Jun 13, 2006 at 12:21:26PM +0100, Andrew Flegg wrote: > >>>>>> If I comment the "uses" lines, it can compile, and execute well after >>>>>> move to 770. But if gtk2 is imported in, it also compile, and don't >>>>>> execute on 770, just reporting: >>>>>> /bin/sh: ./test: not found. >>>>>> >>> What if you try to run it with full path? >>> >> I'd put money on it being the ABI change. The page which smartkenny >> mentioned said it was unpacked from an ARM Linux tarball - this'll no >> longer work, of course. >> > > Ah, it was a Pacal *compiler* and the binary is compiled Pascal binary, > not bytecoded Pascal script run through pcode interpreter? > > Yes, it would need to support EABI for the generated binaries to be able > to interface with the libraries on the target... > > > - Eero > > >
- Previous message: [maemo-developers] Help, executable file dosen't execute.
- Next message: [maemo-developers] Help, executable file dosen't execute.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]