[Lazarus] Building and running Lazarus natively on various architectures

[Mark Morgan Lloyd]

Mark Morgan Lloyd wrote:
> This thread is a summary of intermittent experience over the last year 
> or so with Lazarus running natively on various platforms. I hope to 
> cover ARM, PPC, SPARC and (for completeness) x86 on Linux (Debian v5 
> "Lenny"), possibly also some older Windows OSes on x86 (NT, W2K); I'm 
> afraid that I don't have an x64 system which I think would cover all 
> currently-supported CPUs.
> 
> Mattias, noting your
> 
>> 0.9.29 with fpc 2.4.0 or higher.
> 
> I'll work with sources from svn. This might mean that I'm a day or so 
> behind in some cases since some of the older machines will take more 
> than a day doing a full build.

SPARC on Debian "Lenny"
-----------------------

I initially tried 2.5.1 for this because of a problem in 2.4.0. That 
didn't work due to

Compiling eventcodetool.pas
Compiling extractproctool.pas
Assembling extractproctool
eventcodetool.pas(124,9) Fatal: Syntax error, ")" expected but "," found
Fatal: Compilation aborted

Looking at the source I see

const
   MethodKindAsString: array[TMethodKind] of shortstring = (
         'procedure', 'function', 'constructor', 'destructor',
         'class procedure', 'class function'
         {$IFNDEF VER2_4}
         ,'class constructor', 'class destructor'
         {$ENDIF}
       );

Reverting (?) to 2.4.2-RC1 compiles (make bigide) and executes OK, but 
when loading an existing project or exiting from the IDE I get

$ lazarus
TMainIDE.ParseCmdLineOptions:
   PrimaryConfigPath="/home/markMLl/.lazarus"
   SecondaryConfigPath="/etc/lazarus"
NOTE: miscellaneous options file not found - using defaults
TMainIDE.DoNewProject A
TApplication.HandleException Access violation
   Stack trace:
   $000000CB
WARNING: TLCLComponent.Destroy with LCLRefCount>0. Hint: Maybe the 
component is processing an event?
[TMainIDE.Destroy] A
[TMainIDE.Destroy] B  -> inherited Destroy... TMainIDE
[TMainIDE.Destroy] END
$

These are the same two cases that give 0.9.29 + 2.4.0 problems on armel.

As with armel, lazbuild is OK.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]