Skip to content

compiles on both Windows and Linux#24

Open
Foadsf wants to merge 13 commits into
nasa:masterfrom
Foadsf:dev
Open

compiles on both Windows and Linux#24
Foadsf wants to merge 13 commits into
nasa:masterfrom
Foadsf:dev

Conversation

@Foadsf

@Foadsf Foadsf commented Apr 27, 2024

Copy link
Copy Markdown

now compiles on both Windows and Linux

jasonduley and others added 13 commits December 3, 2015 07:30
writing a python script that finds all the binary files in the repo `python scripts\find_binary.py .`
remove all the binary files with `git filter-branch -f --index-filter "git rm --cached --ignore-unmatch '<./path/to/fileName>'" HEAD`
with both Intel's ifrot and GNU's GFortran
```
The use of 64-bit integers can be specified by -i64 in the cft77 command, INTEGER=64 in the CFT77 control statement, or CDIR$ INTEGER=64 in your program.
```

so I wrapped the lines including the Cray compiler directive (`CDIR$`) like:

```fortran
!DEC$ IF DEFINED(CRAY_COMPILER)
CDIR$ <...>
!DEC$ ENDIF
```

and instructed `ifort.exe` with `/integer-size=64`

this partly solves issue #1 [here](#1)
added some info to README.md
fixes a bunch of fortran issues including #2 and others yet to be opened on GitHub

for example [this one](https://community.hpe.com/t5/operating-system-hp-ux/directive-cdir-integer-64/m-p/7213307/highlight/true#M948824)
…n on Linux Ubuntu WSL

switched to Ninja for faster build
fixes issue #2 and more
Fixed wrong BOZ usage
Fixed link usage to linkup and removed wrong external
Fixed etime usage and removed wrong external
Added compilerflag to allow carriagcontrol
Modified scratch array initialization to match the datatype. Initialization with 0, before string -> most likely resutled in garbage (behavior unknown)
Fixed compile and linking problems:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants