Compilation Errors and Linker Issues in Fortran Code

[Foadsf]

Description

I encountered multiple compilation and linker errors when building the NASTRAN-95 project with Intel oneAPI and the Microsoft Visual Studio toolchain. These include syntax errors with directives, multiple definitions of MAIN__, and unresolved external symbols.

Errors

Compilation Warnings:

The following warnings appear for Fortran files partn3.f, rcard.f, rcard2.f indicating syntax errors with directives:

C:\dev\NASTRAN-95\mis\partn3.f(2): remark #5082: Directive ignored - Syntax error, found '=' when expecting one of: :
CDIR$ INTEGER=64

Similar errors are repeated across the specified files.

Linker Errors:

Linking the Fortran executable results in errors related to multiple definitions and unresolved external symbols:

chkfil.f.obj : error LNK2005: MAIN__ already defined in nastrn.f.obj
shtrmd.f.obj : error LNK2019: unresolved external symbol Q8SHPD referenced in function SHTRMD
C:\dev\NASTRAN-95\bin\nastran.exe : fatal error LNK1120: 3 unresolved externals

Unrecognized Directives:

Additional warnings about unrecognized directives in dsupkc.f:

C:\dev\NASTRAN-95\mds\dsupkc.f(12): remark #5140: Unrecognized directive
CDIR$ NEXTSCALAR

Build Environment

• Compiler: Intel oneAPI
• IDE: Microsoft Visual Studio 2022
• Build tool: CMake, NMAKE

Steps to Reproduce

1. Clone the repository from dev branch and this commit.
2. Run the build process as per the setup instructions using the build.bat script.

Expected Behavior

The project should compile without errors and link all symbols correctly.

Actual Behavior

Compilation stops with syntax errors on Fortran directives, and the linker fails with multiple definitions and unresolved symbols errors.

Possible Solutions

• Review and correct the syntax of the Fortran directive.
• Ensure that there is no duplication in the definition of MAIN__ across different files.
• Verify and ensure all external symbols are defined and correctly linked.

This issue needs attention to correct the errors for a successful build. Any help or insights are welcome!