[fpc-pascal] FPC for ARM

[Thomas Schatzl]

Hi,

Am 28.11.2011 15:18, schrieb Henry Vermaak:
> On 28/11/11 13:41, Juha Manninen wrote:
>> Hi
>>
>> Is FPC 2.2.2 really the latest native release for ARM processors?
>> I guess it can build the more recent versions. (?)
>
> There is an arm release for 2.6.0rc1, but it was built using old
> binutils (last time I checked, at least):
>
> ftp://freepascal.stack.nl/pub/fpc/beta/2.6.0-rc1/arm-linux/

What OS/version are you using? Maybe some OS setup issue? On an HP 
Touchpad and a Sheevaplug-like system, which are both eabi5, the 
bootstrap compiler and fpc produced executables work just fine.

The eabi4 type of the bootstrap compiler originates from the build 
machine running on the latest debian lenny (5.0.9) which unfortunately 
only has very old binutils from 2008 (2.18.x) in its distro, or defaults 
to eabi4 output. At least its GNU as seems to simply ignore a -meabi=5 
assembler switch.

However even that build machine seems to be able to run eabi5 
executables fine. E.g. I copied over the bzip2 executable from an eabi5 
machine to the build machine.

$ objdump -x ./bzip2 | grep ersion
Version References:
private flags = 5000002: [Version5 EABI] [has entry point]
$ ./bzip2 --version
bzip2, a block-sorting file compressor.  Version 1.0.4, 20-Dec-2006.

    Copyright (C) 1996-2006 by Julian Seward.

    This program is free software; you can redistribute it and/or modify
    it under the terms set out in the LICENSE file, which is included
    in the bzip2-1.0.4 source distribution.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    LICENSE file for more details.

bzip2: I won't write compressed data to a terminal.
bzip2: For help, type: `bzip2 --help'.
$ objdump -x /bin/bzip2 | grep ersion
Version References:
private flags = 4000002: [Version4 EABI] [has entry point]

Might not be representative, but it seems to me that your system is 
somewhat oddly configured. (Maybe its some debian thing?)

I do not mind trying to switch to eabi5 by default, but there might be 
systems which absolutely require eabi4 which seems to be some lowest 
common denominator, i.e. also eabi5 setups seem to be able to run them 
anyway.

Thomas