[Solved] Update caused Lazarus to fail

[Avishai]

I installed Lazarus-0.9.28.2-fpc-2.2.2-win32 earlier and everything worked fine.  Now I installed Lazarus-0.9.29-29680-fpc-2.4.2-20110227-win64 (I have an Intel64 processor and Windows7-64).  When I started Lazarus I got the message [Compiler "D:\Lazarus\fpc\2.2.4\bin\i386-win32\fpc.exe" does not support target win64-x86_64].  I reinstalled the original 0.9.28.2-fpc-2.2.2-win32, but I still get the same message about "does not support target win64-x86_64".  What am I doing wrong?  I really need the later version because it has better BiDi support.

[IPguy]

I would start with changing the Lazarus configuration for your 0.9.29-29680 version to point to the fpc 2.4.2 locations.  (should be within the 0.0.29-xxx directory.)

[Avishai]

Thank you, thank you, thank you!  You saved me hours of looking all over the net for a solution.

[Avishai]

Everything was fine until I tried to compile.  It produced a message about the Debugger entering an Error state and won't go any farther.  I checked and the Debugger is set to D:\Lazarus\mingw\bin\gdb.exe

[IPguy]

(I do not have access to my lazarus installation at the moment, so I'm doing this from memory ...)
What is the path to your 0.9.29-xxxxx installation?  Is it D:\Lazarus\...?
If not, I would find the path to gdb.exe within your 0.9.29 software and use the Lazarus configuration tool to point the debugger to the appropriate location.

Also, you can run both fpc and Lazarus from your CLI and review the error messages (if any).  I could give you the command to run if I had access to my Lazarus notes.  There are some hints in the Lazarus wiki on this topic, as I recall.

[Avishai]

The debugger is in fact located at D:\Lazarus\mingw\bin\gdb.exe so that isn't the problem, or at least I don't think so.  I just checked and I can see it running in the Windows Task Manager, so Lazarus is finding it.

[Avishai]

I installed 2.5.1 and that seems to fixed the problem.  Thanks to all that responded to my post