AbsoftTools is not able to interpret linker errors in the same way it does Fortran syntax errors reported by the compiler. You will need to examine the output in the Build window to determine the build failure, starting at the end of the output and working backward.
One of the most common link-time errors is an unresolved reference to an external subroutine.
In this case, the output in the Build window will look something like this:
f95 "./Release/main.o" -o "./project" -IPA:debug=on -IPA:source_pu_order=on -m64 -O2
./Release/main.o: In function `MAIN__':
(.text+0x24): undefined reference to `calc_routine_'
collect2: ld returned 1 exit status
link reported errors.
amake2: **** Error code 1 (continuing)
amake2: `all' not remade because of errors.
Build interrupted
If you are on a Debian based system, you may be getting a bad relocation error because the default on these systems is to create position independent executable programs. The error in the build output for this case will look something like:
/usr/bin/ld: ./Release/main.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
link reported errors.
Build interrupted
To solve this issue, you can turn on the "No PIE" option in the Linker page of the AbsoftTools Project Options dialog.
If you need further assistance, email Absoft support and provide the output from the Build window as well as the name and version of the Linux distribution you running on your system.