[Info-vax] fortran version && Compile the main file in debug mode only
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Wed Aug 26 08:05:15 EDT 2020
Den 2020-08-26 kl. 13:44, skrev HCorte:
> Thanks Hoff, gona ask another question,
>
> have readed that section of B-1 where to use SS$_DEBUG to make/tell a program to start the debugger.
>
> So searched and include the follow: CALL LIB$SIGNAL (%VAL(SS$_DEBUG))
> Tried to compile and gave the error:
>
> This name does not have a type, and must have an explicit type. [SS$_DEBUG]
>
> in that B-1 section its explained:
> You can obtain the definition of SS$_DEBUG at compile time from the appropriate STARLET or SYSDEF file for your language (for example, STARLET.L32 for BLISS or FORSYSDEF.TLB for Fortran)
>
> found in the http://h30266.www3.hpe.com/odl/axplp/progtool/for9590v82/forti64um_009.html#sec_text_libs how to compile with a .TLB (Text librarie)
>
> so tried:
> fort swap+SYS$LIBRARY:FORSYSDEF.TLB/LIBRARY
>
> but still returns the same errors:
> %F90-E-ERROR, This name does not have a type, and must have an explicit type. [SS$_DEBUG]
> %F90-E-ERROR, The data types of the argument(s) are invalid. [%VAL]
>
> still missing some step or that command is not the correct way to include the text library FORSYSDEF.TLB?
>
>
I do not know Fortran that well, but do you not need some "INCLUDE" also?
Keep your SYS$LIBRARY:FORSYSDEF.TLB/LIBRARY and add a line with
INCLUDE '($SSDEF)'
or remove the /LIB thing and add
INCLUDE 'SYS$LIBRARY:FORSYSDEF($SSDEF)'
or define the logical name for the TLB's to search...
More information about the Info-vax
mailing list