Will the suggestions you had posted will also work for XPs?
My cousin's PC is having the same issue. We are thinking of reformatting it-- but of course, that would be our last option...

thank you all
this was the problem
Dino

Several of my F77 projects are giving the following warning message during Build:
"warning: DWARFDebugInfoEntry::AppendDependants() -- check on this item TAG_subrange_type: attr =  AT_upper_bound  form = FORM_ref4"

A couple others give me error "f90fe failed" with no further explanation. This is during the Build process:
("/Applications/Absoft11.0//bin/af90fe -Ap -p. -I/Users/xafs/xas_sources/cmn -I/Users/xafs/xas_sources/plot -Rb -Rp -Rs -N80 -YCOM_NAMES=LCS -YVAR_NAMES=LCS -f77_compat -g -ev -m4 -YMOD_OUT_DIR=./Debug -p./Debug -p/Applications/Absoft11.0//f90includes -F /var/folders/1o/1oVZtVvZGjCD44wWUcRBcU+++TY/-Tmp-//1mnuuB/CALC_CONSTRAINT.l ../../xas_sources/getexafs/CALC_CONSTRAINT.f
f90fe failed.")

Any idea what I can look for to avoid these warnings and errors?

The selection of 'medium' model on a version 7 of the Absoft compiler suggests that the context was 16-bit MSDOS. The 8088/8086 had 'tiny','compact','medium','large' and 'huge' memory models. The solution is to look at the build configuration and remove all options that pertain to a 16-bit OS.

Regarding the fixes specified in the Absoft Tools release notes for v11.04,
"#4 Compilation failure for certain implied do-loops in DATA statements ",
Although the fix in v11.04 is an improvement, there is still a problem :

In the following small program,  DATA statements DS1,DS2, and DS3 (when uncommented) give appropriate error messages (discrepancy between number of values and number of entities)
DS4 should also give a compile error, but it compiles and fills unspecified values with the last specified value ('xx's in this example):
   YLOW  =   ww  ww  ww  xx  xx  xx  xx  xx  xx  xx
   YHIGH =   ww  ww  xx  xx  xx  xx  xx  xx  xx  xx

      PROGRAM v1104
      IMPLICIT NONE
      INTEGER J
      CHARACTER*2 YLOW(10),YHIGH(10)

!      DATA (YLOW(J),J=1,10) /5*'ww',9*'xx'/           !DS1 - compile error (correct)
!      DATA (YLOW(J),J=1,10) /5*'ww',1*'xx'/           !DS2 - compile error (correct)
!      DATA (YLOW(J),YHIGH(J),J=1,10) /5*'ww',19*'xx'/ !DS3 - compile error (correct)
       DATA (YLOW(J),YHIGH(J),J=1,10) /5*'ww',1*'xx'/  !DS4 - compiles(!!) fills with xx's

      write (*,22) YLOW,YHIGH
22    format ('YLOW  = ',10A4,/,'YHIGH = '10A4)
      END


(This has been sent to Absoft support.)

Dino,
What compiler are you using and which switches if any? I assume this is on a Windows system?
What is the statement at line 1368? Are you using Absoft Tools or trying to compile from command line?
From the error message, it looks like you are trying to use some kind of 64-bit option n a 32-bit machine.
Jon

I am just migrating from Absoft v7.5 to Absoft v11.04.
In the attempt to learn the new version I tried to compile and old program (very simple) working on the old version and I get the following message that I was unable to understand .

### Assertion failure at line 1368 of ../../common/com/config.cxx:
### Compiler Error during Back End Driver phase:
### code model `medium' not supported in the 32-bit mode

thank you in advance for the help

Dino Vitale

Within Absoft Tools, if I select the following three lines of Fortran code:
      A=1   ! setup A
      B=2   ! setup B
      C=3
and do the "Edit|Comment" command (Apple-D), only the 3rd line gets commented out, apparently because the other lines already contain a '!' :
      A=1   ! setup A
      B=2   ! setup B
!      C=3


If you start with the lines:
      A=1   ! setup A
!      B=2   ! setup B
      C=3
Again,  just the 3rd line gets a new comment character:
        A=1   ! setup A
!       B=2   ! setup B
!         C=3
So if you follow this with an "Edit|Uncomment" command, you end up with all three lines uncommented out! :
      A=1   ! setup A
      B=2   ! setup B
      C=3

This command worked correctly in v 10, where each Comment command added an '!'  to the beginning of each selected line, whether or not it was already commented out.
This allowed you to easily comment and uncomment blocks of code.

The v11.0.4 Comment command does still work correctly for a single line if the cursor is placed in the line, with no characters selected (highlighted), but there are quicker ways to comment out one line.

Thanks.  Running amakedepend without arguments did give useage, and the arguments look straightforward. 
Since I'm pretty "command line driven", I may try that anyway.  But if that doesn't work, then I'll try the Absoft Tools.
Thanks again.

I was able to get the file clngam.f  from the slatec library to compile
successfully with our 11.0 compiler of OS X by adding a single line:

     EXTERNAL CARG

after the declaration LOGICAL FIRST on line 28 and before the
SAVE statement on line 29. In my modified file, these three lines
read:


      LOGICAL FIRST
      EXTERNAL CARG
      SAVE PI, SQ2PIL, BOUND, DXREL, FIRST