Script Compile Error Cod 1 .Exe Does Something

Does anyone have any idea why I dont know if this is a syntax problem, or if my command.exe does something strange to affect the exit code.

Sorry I couldnt share the full code, but thanks for giving useful feedback given the limited info - guess it is just powershell being buggy as I tried the try catch loop and my.exe runs fine.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Not the answer youre looking for Browse other questions tagged powershell azure-devops or ask your own question.

The video title is Call of Duty 2 SOLUCIN: Script Compile Error by edtskyline, and the authors name is edtskyline, 2021-04-10.

Do not not assume the cause of the error is the same as anyone else who had the same message.

I have attached both the f90 and.for files, and the build log for the.f90 file.

The build log suggests that the problem is with the subroutine VIEW2.

When I try to compile the same F90 source file on my PC desktop, also running Windows 7, it seems to work.

But if it fails only under Parallels Im not sure what we can do about it.

Still, we have fixed many bugs since the 12.0 compiler was initially released so try the current one and see what happens.

I tried compilingthe older fixed format version (.for), but the compiler still aborted.

A colleague of mine also uses Parallels Desktop Windows 7 Intel Fortran Compiler, and she was able to build and run the project, using the same.F90 source code.

Any pointers for troubleshooting I bascially reinstalled everything: Parallels Desktop Windows 7 Intel Fortran Compiler Update 4.

But still no luck.

Any help would be greatly appreciated.

Kaushik.

This may be the (a)problem.

Your main program is using IMPLICIT NONE (good) but it is also using intrinsic functions (e.g.

DSIN(x)) add USE IFPORT to the module USE list.

This same issue resides in other functions and subroutines.

In your.F90 file, line 447 you have a unlabled CONTINUE statement.

This should be innocuous, but you might try removing it.

Lack of proper suffix will affect accuracy in some places an performance in all places.

Also with DBL consider using more accurate value for PI (and make it a parameter).

ELSE IF ( ABS (PHI).GT.

Script Compile Error Cod 1 Free Form It

D-3.AND. NEARLY HORIZONTAL SURFACES The IVF reference guide shows an example like your codeabove, however, in source forms section for free form it states that the must appear at the end of the source line (at least in my reference guide).

Work through the above list and see what happens.

Jim Dempsey ABS (PHI).LT.

THEN UP TO 2 DEG TILT.

In any event, such a thing would not cause an internal compiler error.

I suggest you start cuttung down the source to see what the minimum it takes to show the error.

Ive made further changes and additions to the F90 code and it successfully compiles on my desktop running Windows 7.

The internal error only happens when I am using Parellels Desktop Windows 7 on my macbook.

Steve, Ill try your suggestion about cutting down the source code to find out where the error originates.

But, any other suggestions Could it be a 32- vs 64- bit installation issue I believe I used the 64-bit installation.

Therefore I am thinking that it has to be some installation issue with my software(s).

Anyone have any similar experience The latest F90 file is attached, if it helps.

Thanks. Kaushik.

Hmm - what if you disable warn:interface there Or better, what if you use update 4.

I was passing a string constant as an argument for a subroutine call.