[fpc-devel] Smarter way of generating ARMHF fpc trunk installation?

Jonas Maebe jonas.maebe at elis.ugent.be
Wed Mar 5 20:13:35 CET 2014

On 05 Mar 2014, at 18:21, Thaddy wrote:

> On 5-3-2014 17:06, Jonas Maebe wrote:
>> On 03 Mar 2014, at 09:24, Reinier Olislagers wrote:
>>> make "FPC=/home/odroid/development/fpcbootstrap/arm-linux-ppcarm"
>>> "--directory=/home/odroid/development/fpctrunk/compiler"
>> I just noticed that you are adding -dFPC_ARMH also to CROSSOPT. That does not do anything and can be removed. In combination with your remark at 

> Well, call me a monkey or an ape, but if you leave it out, you get an EABI version of the compiler and EABIHF is missing. Whatever you do, bootstrapped from 2.6.2.
> On both linux and windows you only seem to obtain an EABIHF capable cross compiler if -dFPC_ARMHF is included in both OPT and CROSSOPT and bootstrap with trunk.
> Try it.

Starting with a plain i386 2.6.2 and building trunk on Linux with

make FPC=ppf8 OPT="-dFPC_ARMHF" CPU_TARGET=arm CROSSOPT="-Cparmv7a -CfVFPv3" CROSSBINDIR="/home/jmaebe/diablo/toolchains/armv7-gcc-481-binutils-222-eglibc-217-hard/bin" BINUTILSPREFIX="arm-linux-gnueabi-" all -j 8 FPMAKEOPT="-T 8"

The resulting "ppcarm -i" output:

$ ./ppcarm -i
Free Pascal Compiler version 2.7.1

Compiler Date      : 2014/03/05
Compiler CPU Target: arm

Supported targets:
  Linux for ARMHF
  WinCE for ARM
  GameBoy Advance
  Nintendo DS
  Symbian OS for ARM
  Darwin for ARM
  Android for ARMEL
Supported ABI targets:

Similarly, the cross-compiler also shows that it generates ARMHF code. Note that the above procedure is not really advised, and it's better to first build a native trunk compiler and only then a compiler for another architecture with this first one. But it most definitely results in an ARMHF compiler.


More information about the fpc-devel mailing list