Greetings,

I just tried to cycle a fresh compiler but have a problem with the fpc.exe application.

If I use an old version everything works fine. If I try to use the newly built version I get Access Violations.

If I am in the same directory as the ppc386.exe application for example c:\pp\bin\win32 and run fpc.exe it runs fine. However, if I am someplace else and attempt to run fpc.exe I get the violation.

This first hits when trying to build the rest of the compiler, the packages, fcl, etc. etc. The Make fails because the fpc call to get things like iTO etc. fails. If I force the Make with PP={path}ppc386.exe then everything works fine.

Let me know if more details of what is happening is required.

Not sure if it is related but everytime I cycle the compiler it always errors at the very end when it is doing the compare of the ppc3.exe and ppc386.exe. The file sizes match and everything compares except for about 2-3 bytes. I forget what the line number is.

Not sure about your other problems but the comparison problem between ppc386.exe and ppc3 isn't the problem. I get this often when doing win32 or go32v2 makes (I'm running win9x)... it's something to do with a few bytes of uninitialised memory.

I've fixed it for automatic snapshot makes by replacing the diff.exe & cmp.exe versions you get in the win32 or go32v2 utilities by my own pascal program that doesn't stop when the files are slightly different, but if you do it manually just ignore it!

By the way re your problem the go32v2 and win32 v10 and v11 snapshots (compiler, rtl, ide) have been working every day fine for last 2 weeks or so, with latest sources, starting with the go32v2 and win32 v1.0.10 compilers.

HTH

Regards John

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

John wrote

Not sure about your other problems but the comparison problem between ppc386.exe and ppc3 isn't the problem. I get this often when doing win32 or go32v2 makes (I'm running win9x)... it's something to do with a few bytes of uninitialised memory.

I sort of felt that was what this was about and also I usually ignore it but thought I would mention it in case it was relavent.

As an add on to further clarify my problem.

If I try to say do "make clean" from in my lazarus directory the make will fail with processor errors because it tries to run ".exe" instead of "ppc386.exe" when looking for iTO and the like. This is because the fpc.exe program fails with the Accesses Violation. If I try to run fpc.exe in the same directory as ppc386.exe it finds it and runs fine.

This only happens if I use the newly cycled version of fpc.exe. If I copy the fpc.exe from say the 1.0.11 release and put it in the \pp\bin\win32 directory and again try "make clean" from my lazarus directory everything works fine.