f90doc Problems and Solutions

Windows and VMS

If you want to use f90doc in a Windows or VMS environment, edit the file f90doc and delete the code
    BEGIN {
      my $zero = $0;
      while (-l $zero) {
        my $nextzero = readlink $zero;
        if (substr ($nextzero, 0, 1) eq "/") {
          $zero = $nextzero;
        } elsif ($zero =~ m#^(.*)/#) {
          $zero = "$1/$nextzero";
        } else {
          $zero = $nextzero;
        }
      }
      if ($zero =~ m#(.*)/\w+#) {
        push @INC, "$1/../common/", $1;
      } else {
        push @INC, "../common/", ".";
      }
    }
(which occurs near the top) and replace it with the following:
    BEGIN {
      push @INC, 'directory';
    }
where directory is the name of the directory that contains f90doc and the accompanying .pl files. For example, in Windows, this might be c:\Program Files\f90doc; on VMS, it might be [f90doc.install.directory].

To run f90doc on Windows, type the following at an MS-DOS/Command Prompt:

    perl f90doc file.f90 ...
That is, type perl before f90doc and any arguments.

Thanks to Debora Velarde for testing this out, and to Steven Gould for the pointer on VMS.

sh: --: bad option

If you receive the message ``sh: --: bad option'' when trying to run f90doc, you are on a Linux or similar system that doesn't break #! options into arguments. Download the latest version of f90doc, which fixed this problem.

/usr/bin/env: bad interpreter: No such file or directory

If you receive the message ``/usr/bin/env: bad interpreter'', then you are on a system (e.g., non-UNIX) that does not have env in the directory /usr/bin. That's OK; you don't need env. However, you'll have to replace the first line of f90doc with
    #!/path/to/perl5/bin/perl -w

Last updated November 28, 2010 by Erik Demaine.