FPC 3.3.1b panics when compiling BGRA* component (installed via O.P.M)
!!
lazarus / 64-FPC development

----------------------------------------------------------------------
att2 · 2020-03-22 14:00

Please help me, I have a terrible problem compiling the BGRAControls
package.

My system: VM with Linux Mint 19/Tara with latest updates, LAZ 2.1.0,
FPC 3.3.1beta by install method of latest FPCUPDeluxe 1.8.6d.

Trying to install BGRAControls via Online-Package-Manager gives
compile error :   

Kompiliere Package bgracontrols 6.6.1: Access violation
  $0000000000536ACD
  $0000000000536CCE
  $00000000009C6560  EXECUTE,  line 1603 of exttools.pas
, Fehler: 4, Warnungen: 6, Hinweise: 2
bctools.pas(281,3) Warning: Case statement does not handle all
possible cases
bctools.pas(581,14) Hint: Local variable "p" of a managed type does
not seem to be initialized
bctools.pas(670,3) Warning: Case statement does not handle all
possible cases
bceffect.pas(184,3) Warning: Case statement does not handle all
possible cases
bceffect.pas(224,3) Warning: Case statement does not handle all
possible cases
bcfilters.pas(320,21) Hint: Local variable "gpallete" of a managed
type does not seem to be initialized
bcfilters.pas(797,3) Warning: Case statement does not handle all
possible cases
Warning: Recompiling BGRASliceScaling, checksum changed for /home/arm2
/programme/lazarus/config_lazarus/onlinepackagemanager/packages/bgrabi
tmap-master/bgrabitmap/lib/x86_64-linux/3.3.1/bgrabitmap.ppu
Panic: interner Fehler: Access violation
Panic: interner Fehler:   $0000000000536ACD
Panic: interner Fehler:   $0000000000536CCE
Panic: interner Fehler:   $00000000009C6560  EXECUTE,  line 1603 of
exttools.pas

-----------

Now what to do ? How to install it ? Is it a bug in the FPC? What is
this ?

----------------------------------------------------------------------
marcov · 2020-03-22 14:05

exttools is part of Lazarus (the IDE itself). So without more info,
I'd say it is a lazarus issue.

But I compiled bgra with 3.3.1  (and lazarus trunk) over opm as recent
as last friday and haven't had this error.

So reproducing and isolating will be hard, and anything you can do to
pinpoint the problem will be welcome.

----------------------------------------------------------------------
AL · 2020-03-22 14:13

Have you tried the "clean and build" option?