Trying to compile lazarus with trunk fpc:

Any ideas?

make.exe[2]: Entering directory `C:/lazarus_latest/ide' C:/FPC/trunk_gw/bin/i386-win32/fpc.exe -gl -dlclwin32 -Fu../lcl/units/i386-win32 -Fu../lcl/units/i386-win32/win32 -Fu../components/codetools
/units/i386-win32 -Fu../components/lazutils/lib/i386-win32 -Fu../components/synedit/units/i386-win32
-Fu../components/lazcontrols/lib/i386-w
in32 -Fu../components/custom -Fu../components/mpaslex -Fu../ideintf/units/i386-win32 -Fu../designer -Fu../debugger -Fu../debugger/frames -Fu
../converter -Fu../packager -Fu../packager/frames
-Fu../packager/units/i386-win32 -Fu../units/i386-win32 -Fuframes -Fu. -Fiinclude -Fiinclud
e/win32 -Fi../images -FE.. -FU../units/i386-win32 -WG -gh -g -gw -godwarfsets -gl -dCR -Ct -Co -Cr -Ci -gt -Sa -dXe -Se10 -ve -vw - vn -vi -OpPENTIUMM -O1 -CX -WC -dVerboseDebugger -dDBG_VERBOSE -dDBG_VERBOSE_BRKPOINT -dDBG_STATE -dDBG_DATA_MONITORS -dDBG_LOCATION_ INFO -dDBGMI_QUEUE_DEBUG -dDBGMI_WITH_DISASS_OVERFLOW -dDBG_WITH_DEBUGGER_DEBUG -dSynCheckPaintLock -dSynClipboardExceptions -dAssertSynMemI
ndex -dSynAssert -dSynAssertFold -dWithSynOverviewGutter @C:\laz_configs\lazarus_latest\idemake.cfg -FEC:\lazarus_latest -olazarus.new.exe -
di386 lazarus.pp
Free Pascal Compiler version 2.7.1 [2011/10/08] for i386 Copyright (c) 1993-2011 by Florian Klaempfl and others Target OS: Win32 for i386
Compiling lazarus.pp
Fatal: Compilation aborted

I tried in gdb

Compiling lazarus.pp
Fatal: Compilation aborted
An unhandled exception occurred at $0041DB1E :
EListError : List index exceeds bounds (2273)
$0041DB1E TFPLIST__RAISEINDEXERROR, line 639 of cclasses.pas

Error: C:\FPC\trunk_gw\bin\i386-win32\ppc386.exe returned an error exitcode (normal if you did not specify a source file to be compiled) =thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1",exit-code="01"
*stopped,reason="exited",exit-code="01"
(gdb)
bt
&"bt\n"
&"No stack.\n"
^done
(gdb)

I understand that Lazarus will not be able to run with the "NewString" version of FPC.

Semmingly it can't even be compiled.

-Michael

Michael Schnell wrote

I understand that Lazarus will not be able to run with the "NewString" version of FPC.

Strange logic. How you decided that if something does not do now it will not be able to do the same at future.

Semmingly it can't even be compiled.

I think the issue Martin reports is not related to the "NewString" at all.

Best regards,
Paul Ishenin

Paul Ishenin wrote

Strange logic. How you decided that if something does not do now it will not be able to do the understand that the type "String" will change it's behavior (please

correct me if I'm wrong).
I understand that Lazarus might use assumptions regarding "String"s that might not be applicable any more (please correct me if I'm wrong).

OTOH I understand that Lazarus will happily follow the move to "NewStrings" and some later version will use them as a decent improvement regarding the current "UTF-8 code stored in a variable of a type called ANSIString" paradigm" (please correct me if I'm wrong).

-Michael