On 09/14/2017 09:59 PM, Peter Robinson wrote:
How do you want to proceed? We have a hacked glibc in F26 and earlier which
happens to run FPC softfloat binaries with the old program interpreter. I
can restore that to F27 and rawhide if this helps to restore armhfp/EABIHF
support, but maybe this is counterproductive because it obscures problems.
Can I bootstrap the newer 3.0 release using the fpc-2.6.2-4.fc20
build? If so I can deal with this.
I tried that, but I got this for the master branch:
ppcarm -Ur -Ur -Xs -O2 -n -Fi../inc -Fi../arm -Fi../unix -Fiarm -FE.
-FU/tmp/fpc/fpcbuild-3.0.2/fpcsrc/rtl/units/arm-linux -k"--build-id" -gl
-darm -dRELEASE -Fi../objpas/sysutils ../unix/sysutils.pp
syshelph.inc(40,31) Error: Identifier not found "Helper"
syshelph.inc(40,31) Error: Error in type definition
syshelph.inc(40,31) Error: Can't create unique type from this type
syshelph.inc(40,31) Fatal: Syntax error, ";" expected but "FOR" found
Fatal: Compilation aborted
Makefile:3536: recipe for target 'sysutils.ppu' failed
fpc-3.0.0-1.fc24.armv7hl is able to build it, but has already switched
to soft-float.
fpc-2.6.4-2.fc23.armv7hl is still okay, but fails to build in the same
place. I can partially build fpc 3.0.0 with it, but that's where the
ABI regression happens. The ABI regression is avoided if I delete the
/lib/ld-linux.so.3 symbolic link first. However, that doesn't help with
building with the regressed compilers because they have lost EABIHF
support (they only support a single ABI variant).
Well, looking back at the history, I found this:
commit 62ea5a56cb91c1688d01a7e8df266af798632045
Author: Joost van der Sluis <joost@xxxxxxx>
Date: Sat Jan 9 17:18:56 2016 +0100
Bootstrap ARM using cross-compiled armhl binaries, because the
(patched) 2.6.4-ARM compiler in the repository is not able to
compile the
3.0.0 release.
That probably explains the ABI regression. ppcarm found in the tarball
has the wrong path for the program interpreter.
Florian
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
