Build fails for no apparent reason

[WSinc]

When I just added a new routine PAWN, it tells me that there are TWO MAIN programs.
When I remove that routine, it builds with no problems, providing I remove the CALL to it.

All routines in the project compiled with no errors or warnings

The PAWN routine has the exact same interface as 5others, so I don't see
why it would trigger this error message. I don't see anyhting unusual about it, in other words.

I am wondering if "stripping the guts out" wouldallow itto complete the build.
I will experiment further.

The enclosed archive was made with 7-ZIP, its supposed to be compatible.

Could this be an environmental concern? I tunred off the SPYWARE, and did a reboot, same result.

Any ideas?

[IanH · Accepted solution]

Right at the bottom of pawn.f90 (line 47, ten lines below the rest of the code) you have a stray END statement. An end statement on its own is valid - it defines a empty main program. That empty main program clashes with your other "intended" main program.

[WSinc]

Boy, I never would have caught that ! ! !

But why wouldn't it look for a PROGRAM statement?

It seems rather strange, anyway - - - -

[Steven_L_Intel1]

PROGRAM statement is optional - as Ian says, an END not preceded by a SUBROUTINE, FUNCTION, BLOCK DATA or MODULE, ends a main program.