KIND =2 vs KIND = 3 conflict - when debugging

HI.

I often get a error message when of the type 'variable is KIND(3) when a KIND(2) was expected' when only part of the project complied using /full_debug. I use implicit none and and all floating point variables are declared as double precision (ftn77 fixed format style code) . could this be an issue with the extra information requires for debugging?

I would need to see the context in the code in order to determine whether or not this is a valid error report.

If it is a run time error when calling a subprogram then I would need to see both ends of the call.

on reflection I suspect it could be that the called function is compiled in ftn77 and is embedded in a legacy .LIB library.