Hi
My problem still persists.
Here are the details of 2 binaries - first compiled using fpc-arm and
second qt4 for arm. The second one is working,
1.
debian-armel:~# readelf -h firework
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: ARM
Version: 0x1
Entry point address: 0x8f1c
Start of program headers: 52 (bytes into file)
Start of section headers: 260800 (bytes into file)
Flags: 0x5000002, has entry point, Version5 EABI
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 6
Size of section headers: 40 (bytes)
Number of section headers: 34
Section header string table index: 31
2.
debian-armel:~# readelf -h framebuffer
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: ARM
Version: 0x1
Entry point address: 0x8874
Start of program headers: 52 (bytes into file)
Start of section headers: 10272 (bytes into file)
Flags: 0x5000002, has entry point, Version5 EABI
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 8
Size of section headers: 40 (bytes)
Number of section headers: 27
Section header string table index: 26
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: ARM
Version: 0x1
Entry point address: 0x8f1c
Start of program headers: 52 (bytes into file)
Start of section headers: 260800 (bytes into file)
Flags: 0x5000002, has entry point, Version5 EABI
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 6
Size of section headers: 40 (bytes)
Number of section headers: 34
Section header string table index: 31
2.
debian-armel:~#ldd firework
/usr/bin/ldd: line 116: ./firework: No such file or directory
debian-armel:~# ldd framebuffer
libdl.so.2 => /lib/libdl.so.2 (0x4002d000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x40038000)
libm.so.6 => /lib/libm.so.6 (0x40113000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x401c0000)
libc.so.6 => /lib/libc.so.6 (0x401d4000)
/lib/ld-linux.so.3 (0x40000000)
On Tue, Aug 25, 2009 at 7:48 PM, Henry Vermaak<henry.verm...@gmail.com> wrote:
> 2009/8/25 Nataraj S Narayan <natara...@gmail.com>:
>> Hi Henry
>>
>> Not any particular reason for that. Company policy was to get rid of
>> Angtrom and go for Debian.
>>
>> Well seems debian-armel is also EABI 4. Would you suggest me a RFS with EABI
>> 5?
>
> I'm just saying that you won't have these problems if you stick to the
> same toolchain. There may still be issues with the fpc armel port,
> but that's a different matter.
>
> Henry
> _______________________________________________
> fpc-pascal maillist - fpc-pascal@lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal
>
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
