compproc.inc  Error: Fields cannot appear after a method or property
definition
lazarus / 1-Linux

----------------------------------------------------------------------
BriggsBFC · 2017-01-09 20:00

Hi,

I followed the instructions here: http://wiki.lazarus.freepascal.org/A
ndroid_tutorial#Rebuild_Lazarus_IDE

But when I compile with:
make crossinstall CPU_TARGET=arm OS_TARGET=linux
CROSSBINDIR=~/Android/android-ndk-r13b/toolchains/arm-linux-
androideabi-4.9/prebuilt/linux-x86_64/arm-linux-androideabi/bin
OPT=-dFPC_ARMEL INSTALL_PREFIX=~/Android/fpcsrc/Makefile

I get the following compiler errors:
compproc.inc(64,91) Error: Fields cannot appear after a method or
property definition, start a new visibility section first
compproc.inc(65,102) Error: Fields cannot appear after a method or
property definition, start a new visibility section first
compproc.inc(66,94) Error: Fields cannot appear after a method or
property definition, start a new visibility section first
compproc.inc(320,114) Error: Fields cannot appear after a method or
property definition, start a new visibility section first
compproc.inc(320,136) Fatal: There were 4 errors compiling module,
stopping
Fatal: Compilation aborted


I'm new to Lazarus, any help would be appreciated.

----------------------------------------------------------------------
Cyrax · 2017-01-09 20:37

Which version of FPC you are using?

----------------------------------------------------------------------
BriggsBFC · 2017-01-10 10:30

I downloaded the latest version of FPC with:
svn co http://svn.freepascal.org/svn/fpc/trunk/ ~/Android/fpcsrc

It would appear I have Version 3.1.1

----------------------------------------------------------------------
marcov · 2017-01-10 10:45

From the little info that you give, an educated guess would be that
you run a separate install makefile step with the globally installed
compiler, while you probably should pass the compiler generated in
some previous build step. 
(PP=c:\fpc\newlygenerated\compiler\ppccrossarmhf or something)

Or it tries to trigger an install without a build (all) step, and then
it should be the release compiler (globally installed or manually
passed like above)

----------------------------------------------------------------------
lmcmillan · 2020-06-10 17:43

Silly as it was, I got this error once because I used "string:"
instead of "string;"  That is, I mis-typed and put a colon in there
instead of a semi-colon.  It was in the implementation section of a
unit, and gave me that error.

----------------------------------------------------------------------
PascalDragon · 2020-06-11 09:16

No, in the case of BriggsBFC it was definitely a compiler mixup,
because back then I had extended compilerproc to take an optional
:INTCONST and older 3.1.1 compilers did not support that (the code
inside compproc.inc only protected that against the 3.0.x series).