pe.exe and pec.exe do not work when built with vac365

[abwillis]

Pe.exe, pec.exe and I think pe2lx.exe do not work when built with vac365. I can replace pe.exe and pec.exe with ones built with vac308 and then all works so it is specific to those executables. I have not tried pe2lx to see if it works but it seemed to fail when I ran it as a test. These fail silently, there is no error message displayed and no entry in popuplog.os2 that I have found. These did work ok at one time as I used to build Odin with VAC365 years ago and I don't recall a problem myself nor do I recall anyone reporting an issue with the builds I had uploaded.

[abwillis]

pe2lx did not give a message and no popuplog entry but pe.exe and pec.exe do.

12-27-2010 16:40:31 SYS3175 PID 4a82 TID 0001 Slot 00cf E:\SVN-CODE\ODIN32\BIN\PE.EXE c0000005 00023e4b P1=00000001 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=001406d4 ECX=000403bc EDX=001406f8 ESI=001406d4 EDI=00000000 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:00023e4b CSACC=f0df CSLIM=ffffffff SS:ESP=0053:001404ac SSACC=f0f3 SSLIM=ffffffff EBP=00140544 FLG=00012206

PE.EXE 0002:00003e4b

---

12-27-2010 16:40:34 SYS3175 PID 4a83 TID 0001 Slot 00cf E:\SVN-CODE\ODIN32\BIN\PEC.EXE c0000005 00023e6b P1=00000001 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=001406d4 ECX=000403bc EDX=001406f8 ESI=001406d4 EDI=00000000 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:00023e6b CSACC=f0df CSLIM=ffffffff SS:ESP=0053:001404ac SSACC=f0f3 SSLIM=ffffffff EBP=00140544 FLG=00012206

PEC.EXE 0002:00003e6b

[Silvan Scherrer]

this is all possible. some header are changed and have ifdef included for vac308 and gcc. probably vac365 thinks it's gcc. as you can see on other tickets we will switch compiler to gcc anyway (sonner or later). so we can't support vac365 also right now.

[abwillis]

With change to GCC compiler this is no longer an issue.