Latest Lazarus/FPC 2.4.0 SVN

Is it a my problem? Yesterday, all was fine.
(I have a script that download and compile everything automatically when I want)

...
...
...
Free Pascal Compiler version 2.4.0 [2010/09/15] for i386
Copyright (c) 1993-2009 by Florian Klaempfl
Target OS: Win32 for i386
Compiling imagesforlazarus.pas
Compiling lazpng.pas
Compiling lazpnm.pas
Compiling lazjpg.pas
Compiling lazbmp.pas
Compiling laztga.pas
Compiling lazxpm.pas
imagesforlazarus.pas(10,9) Hint: Unit "LazPNG" not used in ImagesForLazarus
imagesforlazarus.pas(10,17) Hint: Unit "LazPNM" not used in ImagesForLazarus
imagesforlazarus.pas(10,25) Hint: Unit "LazJPG" not used in ImagesForLazarus
imagesforlazarus.pas(10,33) Hint: Unit "LazBMP" not used in ImagesForLazarus
imagesforlazarus.pas(10,49) Hint: Unit "LazXPM" not used in ImagesForLazarus
267 lines compiled, 0.3 sec
7 hint(s) issued
"Compiling package ImagesForLazarus 1.0.1" completed
TLazPackageGraph.CheckIfPackageNeedsCompilation  No state file for TurboPowerIPr
o 1.0
FindFPCTool Executable="fpcmake.exe" CompilerFilename="C:\Develop\fpc\2.4.0\bin\
i386-Win32\fpc.exe"
FindFPCTool Try="C:\Develop\fpc\2.4.0\bin\i386-Win32\fpcmake.exe
An unhandled exception occurred at $004DA35D :
EAccessViolation : Access violation
  $004DA35D  TLAZPACKAGEGRAPH__WRITEMAKEFILE,  line 3528 of C:/Develop/lazarus/p
ackager/packagesystem.pas
  $004D8746  TLAZPACKAGEGRAPH__COMPILEPACKAGE,  line 3151 of C:/Develop/lazarus/
packager/packagesystem.pas
  $004D8309  TLAZPACKAGEGRAPH__COMPILEREQUIREDPACKAGES,  line 3035 of C:/Develop
/lazarus/packager/packagesystem.pas
  $00402D52  TLAZBUILDAPPLICATION__COMPILEAUTOINSTALLPACKAGES,  line 514 of lazb
uild.lpr
  $00402AC5  TLAZBUILDAPPLICATION__BUILDLAZARUSIDE,  line 457 of lazbuild.lpr
  $00404AC8  TLAZBUILDAPPLICATION__RUN,  line 1007 of lazbuild.lpr
  $004060F1  main,  line 1220 of lazbuild.lpr

Regards,
Kjow

--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply via email to