• Linux x86/x86_64 - After installation, I receive the message "Unable to obtain license: license server not found" or "Unable to obtain license: license not found." How do I fix this?

    Single User Licenses:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually /opt/absoftXXXX where XXXX represents the product version number)

    2) If your license file does not contain a line which reads "SERVER: 127.0.0.1", add this line at the top of the file.

    3) Verify that there is a line which begins with "LICENSE:" If there is a line which begins with "PRO:", replace "PRO:" with "LICENSE:"

    4) Verify that the string following "LICENSE:" does not contain any dashes ("-").

    5) If you made any changes, save the license file in plain text format.

    6) Kill any currently running Absoft license server using "killall clmd_absoft" or reboot your computer. Re-test.

    7) If you still receive the error, send an email to support@absoft.com which includes the name and version of your Linux distribution and hardware platform. 

    * Please attach your license.dat file as well as the file named "absoft_release" from the Absoft installation folder.

    Multiple User Licenses:

    1) Send an email to support@absoft.com which includes the operating system and hardware information for the system on which you are running the Absoft license server and for the client which is unable to obtain a license. 

    *Attach the license.dat files from the server and from the client which is unable to obtain a license.

  • Linux x86/x86_64 - Are Unix and Vax subroutines such as DATE, TIME, GETARG, IARGC, etc, supplied with the Absoft compiler?

    Complete Unix and Vax compatibility libraries are provided with the Absoft compiler. They are documented in the Absoft manual "SupportLibrary.pdf" in the Absoft documentation directory. Several methods of accessing the library are available. The easiest is with the Absoft Developer Tools Interface. From the Project menu, select Default Tool Options. In the General options section, check the Unix Library or the Vax Library check box.

    Fortran 90/95 modules are also provided for these libraries. Simply add a USE statement to use program. 

    For example:

    use vax_library
    character*20 thedate
    call date(thedate)
    print *,thedate
    end

    use unix_library
    character*24 tim
    tim = ctime(5)
    write (*,*) tim
    end

  • Linux x86/x86_64 - Can I generate 32 bit programs on my 64 bit system?

    Yes. The 64 bit version of Absoft Fortran 95 can also generate 32 bit programs. You will need to have the 32 bit versions of the standard Linux development tools installed in order to use this capability. If you are able to compile a simple 32 bit C program using gcc -m32, you have these tools installed.

  • Linux x86/x86_64 - Can I use more than 2 GB of memory on a 32-bit system?

    There are 2 limitations.

    First, by default the compiler uses the small code model. This limits all code + static data to approximately 2GB, but allows for more efficient code. Using the option -mcmodel=medium will raise this limit.

    Second, there is a limitation in the GNU assembler that limits individual common blocks to being less than 2GB in size.This limitation has been lifted in the assembler included with binutils 2.14 and later.

  • Linux x86/x86_64 - How can I modify the default behavior of the Absoft runtime library?

    The runtime library checks for an environment variable named ABSOFT_RT_FLAGS on entry to the first I/O statement in a program.

    The following switches can be specified using this variable:

    -defaultcarriage:
    Causes the units preconnected to standard output to interperet carriage control characters as if they had been connected with ACTION='PRINT'.

    -fileprompt: 
    Causes the library to prompt the user for a filename when it implicitly opens a file as the result of I/O to an unconnected unit number. By default, the library creates a filename based on the unit number.

    -vaxnames: 
    Causes the library to use 'vax style' names (FORnnn.DAT) when creating a filename as the result of I/O to an unconnected unit number.

    -unixnames: 
    Causes the library to use 'unix style' names (fort.nnn) when creating a filename as the result of I/O to an unconnected unit number.

    -bigendian: 
    Causes the library to interpret all unformatted files using big endian byte ordering.

    -littleendian: 
    Causes the library to interpret all unformatted files using little endian byte ordering.

    -noleadzero: 
    Causes the library to surpress the printing of leading zeroes when processing an Fw.d edit descriptor. This only affects the limited number of cases where the ANSI standard makes printing of a leading zero implementation defined. 

    -reclen32: 
    Causes the library to interpret the value specified for RECL= in an OPEN statement as 32-bit words instead of bytes. 

    -f90nlexts:
    Allows f90 namelist reads to accept non-standard syntax for array elements. Without this flag, the following input results in a runtime error:

    $ONE

    A(1)=1,2,3,4

    $END

    When -f90nlexts is set, the values are assigned to the first four elements of A.

    -connectunit9
    Causes UNIT 9 to be preconnected to standard input and output.

    -maceol
    Formatted sequential files are in Classic Macintosh format where each record ends with a carriage return.

    -doseol
    Formatted sequential files are in Windows format where each record ends with a carriage return followed by a line feed.

    -unixeol
    Formatted sequential files are in Unix format where each record ends with a line feed.

    -hex_uppercase
    Data written with the Z edit descriptor will use upper case characters for A-F.

    To set ABSOFT_RT_FLAGS:

    export ABSOFT_RT_FLAGS=-fileprompt

    *Note: the leading minus sign is required for each switch and multiple switches must be separated by one or more spaces.

  • Linux x86/x86_64 - How do I install my Absoft compiler?

    Use the following instructions to install the product.

    This document describes the steps required to correctly install Absoft Fortran 95 for Linux systems:

    1. Installation. 
    2. Setting environment variables. 
    3. Optional packages. 
    4. Source code availability

    STEP 1: To install Absoft Fortran 95, please run the installation script as root, alternatively you can install as a normal user however this configuration is not recommended. The installation script is located in the root directory on the CD-ROM, to run simply type: 

    ./install 

    NOTE: If you are installing this product from a CD-ROM and the install script fails to run, it is likely that your system has mounted the CD-ROM without execute permission. Execute permission can be added to an already mounted CD-ROM using the mount command. An example:

    mount -o remount,exec (mount_point or device) 

    where (mount_point or device name) is replaced by the actual mount point or device name for your system. See the manual page for mount for further information. 

    Your Absoft Pro Fortran serial number can be found on the inside front cover of the CD case or in your delivery email.

    STEP 2: Before using this package, you need to create the ABSOFT environment variable and add the directory containing the Fortran 95 tools to your PATH environment variable. You should also add the appropriate set of commands to your startup script to avoid having to do this step each time you want to use the compilers. 

    If you are using bash, ksh, or sh, enter 

    ABSOFT=/opt/absoft11.0 
    PATH=$ABSOFT/bin:$PATH 
    export ABSOFT PATH 

    and add these commands to .bash_profile or .bashrc file in your home directory. 

    If using csh or tcsh, enter 

    setenv ABSOFT /opt/absoft11.0 
    set path = ( $path $ABSOFT/bin ) 

    and add these commands to .tcshrc or .cshrc file in your home directory. 

    STEP 3: If you would like to use the -fast_math option (AMD only!) you will need to install an additional package. 

    libf2c: 

    f2c is a library that is necessary for linking to the AMD ACML libraries. Most major linux distributions come with this library, however it is generally not installed by default. Please install this package with the package manager provided with your distribution of Linux. Note: a few Linux distributions have renamed libf2c to libg2c. If you are using one of these distributions, you will need to specify the -use_g2c optin when using the -fast_math option. 

    STEP 4: If you are interested in obtaining the source code for the open source components listed in licenses/Copyrights_and_Licenses.pdf please follow the appropriate step below: 

    1. If you received a physical distribution of this product the source code is in the source directory on the CD 

    2. If you received a electronic delivery of this product please email sales@absoft.com to request the source code for the open source components included with this product. 

    DOCUMENTATION Your documentation files have been installed in the directory $ABSOFT/doc. These files are in .pdf format and require a pdf reader in order to view them.

  • Linux x86/x86_64 - How do I link to libraries?

    All libraries supplied with the Absoft compiler (such as LAPACK) are built with all external symbols folded to lower case with trailing underscores. The required options for linking to these libraries are:

    f90: -YEXT_NAMES=LCS, -YEXT_SFX=_

    f77: -f -N15

    NOTE: These are default options for Pro Fortran V10.1.

    To link with other third party libraries, it is necessary to determine how the external symbol names are presented (case folding and decoration) and use the appropriate compiler options.

  • Linux x86/x86_64 - How do I solve stack overflow problems?

    The default for Pro Fortran is an 8 megabyte stack. Use the bash ulimit command to raise the stack size limit (the csh equivalent is 'limit stack'). For example, # ulimit -s 32768. Once raised the limit applies to the current process and any children of that process.

    Alternately, you can use the -s compiler option to program storage from the stack to the heap.

  • Linux x86/x86_64 - How do I upgrade a trial license with a purchased license without re-installing?

    To replace a trial license with a purchased license:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually /opt/absoftXXXX where XXXX represents the product version number) 

    2) Delete the license string that follows the word "LICENSE:" 

    3) Type in your new license string without the dashes. 

    4) Save the license file in plain text format. 

    5) Kill any currently running Absoft license server using "killall clmd_absoft" or reboot your computer.

  • Linux x86/x86_64 - How do I use the IMSL libraries?

    NOTE: The IMSL library is built with all external symbols folded to lower case with trailing underscores.

    If you are building your program with the Absoft Developer Tools Interface, simply select Default Tool Options from the Project Menu, choose General options, and click the IMSL check box. The Absoft Developer Tools Interface will add all of the necessary compiler options and libraries.

    To use the library from the command line, the necessary environment variables were established when the library was installed. Refer to the following document for complete details on using the library from the command line:

    /opt/CTT6.1/notes/f90/absoft_32/quickstart

    Or:

    /opt/CTT6.1/notes/f90/absoft_64/quickstart

  • Mac OS X Intel - After installation, I receive the message "Unable to obtain license: license server not found" or "Unable to obtain license: license not found." How do I fix this?

    Single User Licenses:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually /Applications/AbsoftXXXX where XXXX represents the product version number)

    2) If your license file does not contain a line which reads "SERVER: 127.0.0.1", add this line at the top of the file.

    3) Verify that there is a line which begins with "LICENSE:" If there is a line which begins with "PRO:", replace "PRO:" with "LICENSE:"

    4) Verify that the string following "LICENSE:" does not contain any dashes ("-").

    5) If you made any changes, save the license file in plain text format.

    6) Reboot your computer and test.

    7) If you still receive the error, send an email to support@absoft.com which includes your operating system version (OS X 10.4 Tiger or OS X 10.5 Leopard) and hardware platform.

    *Please attach your license.dat file as well as the file named "absoft_release" from the Absoft installation folder.

    Multiple User Licenses:

    1) Send an email to support@absoft.com which includes the operating system and hardware information for the system on which you are running the Absoft license server and for the client which is unable to obtain a license.

    *Attach the license.dat files from the server and from the client which is unable to obtain a license.

  • Mac OS X Intel - Are Unix and Vax subroutines such as DATE, TIME, GETARG, IARGC, etc, supplied with the Absoft compiler?

    Complete Unix and Vax compatibility libraries are provided with the Absoft compiler. They are documented in the Absoft manual "SupportLibrary.pdf" in the Absoft documentation directory. Several methods of accessing the library are available. The easiest is with the Absoft Developer Tools Interface. From the Project menu, select Default Tool Options. In the General options section, check the Unix Library or the Vax Library check box.

    Fortran 90/95 modules are also provided for these libraries. Simply add a USE statement to use program. 

    For example:

    use vax_library
    character*20 thedate
    call date(thedate)
    print *,thedate
    end

    use unix_library
    character*24 tim
    tim = ctime(5)
    write (*,*) tim
    end

  • Mac OS X Intel - How can I modify the default behaviour of the Absoft runtime library?

    The runtime library checks for an environment variable named ABSOFT_RT_FLAGS on entry to the first I/O statement in a program.

    The following switches can be specified using this variable:

    -defaultcarriage:
    Causes the units preconnected to standard output to interperet carriage control characters as if they had been connected with ACTION='PRINT'.

    -fileprompt: 
    Causes the library to prompt the user for a filename when it implicitly opens a file as the result of I/O to an unconnected unit number. By default, the library creates a filename based on the unit number.

    -vaxnames: 
    Causes the library to use 'vax style' names (FORnnn.DAT) when creating a filename as the result of I/O to an unconnected unit number.

    -unixnames: 
    Causes the library to use 'unix style' names (fort.nnn) when creating a filename as the result of I/O to an unconnected unit number.

    -bigendian: 
    Causes the library to interpret all unformatted files using big endian byte ordering.

    -littleendian: 
    Causes the library to interpret all unformatted files using little endian byte ordering.

    -noleadzero: 
    Causes the library to surpress the printing of leading zeroes when processing an Fw.d edit descriptor. This only affects the limited number of cases where the ANSI standard makes printing of a leading zero implementation defined. 

    -reclen32: 
    Causes the library to interpret the value specified for RECL= in an OPEN statement as 32-bit words instead of bytes. 

    -f90nlexts:
    Allows f90 namelist reads to accept non-standard syntax for array elements. Without this flag, the following input results in a runtime error:

    $ONE

    A(1)=1,2,3,4

    $END

    When -f90nlexts is set, the values are assigned to the first four elements of A.

    -connectunit9
    Causes UNIT 9 to be preconnected to standard input and output.

    -maceol
    Formatted sequential files are in Classic Macintosh format where each record ends with a carriage return.

    -doseol
    Formatted sequential files are in Windows format where each record ends with a carriage return followed by a line feed.

    -unixeol
    Formatted sequential files are in Unix format where each record ends with a line feed.

    -hex_uppercase
    Data written with the Z edit descriptor will use upper case characters for A-F.

    To set ABSOFT_RT_FLAGS using bash, open the terminal and enter:

    export ABSOFT_RT_FLAGS=-fileprompt

    To set ABSOFT_RT_FLAGS using tcsh, open the terminal and enter:

    setenv ABSOFT_RT_FLAGS -fileprompt

    *Note: MRWE applications must be launched from the command prompt so that the ABSOFT_RT_FLAGS will be used.

  • Mac OS X Intel - How do I install my Absoft compiler?

    Use the following instructions to install the product.

    STEP 1:

    After inserting the Absoft Pro Fortran CD-ROM into your CD Drive, you will see an icon labeled 'AbsoftProFortran95'. This is the installer you need to run.

    To start the installation, double click on the icon. You will be prompted for your administrator name and password. After entering this information the installation process will begin and you will be prompted to enter your name, company name, and the serial number of your Pro Fortran software. 

    You must enter your name and the serial number to complete the installation.

    Your Absoft Pro Fortran serial number can be found on the inside front cover of the CD case or in your delivery email.

    STEP 2:

    Absoft Pro Fortran relies on several components from the Xcode Tools package. Before using Pro Fortran, please make sure you have Xcode installed. Depending on the version of OS X you are using, there are a few possible locations for this package:

    A) Check your OS X distribution media; you may already have an Xcode CD

    B) Check for an Xcode package in the Installers folder located in Applications

    C) You may download Xcode from http://www.apple.com

    STEP 3:

    If you wish to run Pro Fortran from the command line, you will need to modify your shell startup script to set up some environment variables. If you are using bash, add the following lines to the .bash_profile in your home directory: (If you don't have a .bash_profile, create one with these lines in it)

    export ABSOFT=/Applications/Absoft11
    export PATH=$ABSOFT/bin:$PATH

    If you are using a different shell, refer to that shell's documentation for the correct syntax for setting and exporting environment variables.

    You will need to restart the Terminal Application before these changes will take effect.

    Please see the document 'Pro Fortran 11 Release Notes.pdf' for additional information about Pro Fortran.

  • Mac OS X Intel - How do I link to libraries?

    All libraries supplied with the Absoft compiler (such as LAPACK) are built with all external symbols folded to lower case with trailing underscores. The required options for linking to these libraries are:

    f90: -YEXT_NAMES=LCS, -YEXT_SFX=_

    f77: -f -N15

    NOTE: These are default options for Pro Fortran V10.1.

    To link with other third party libraries, it is necessary to determine how the external symbol names are presented (case folding and decoration) and use the appropriate compiler options.

  • Mac OS X Intel - How do I solve stack overflow problems?

    The default for Pro Fortran is an 8 megabyte stack. Use the bash ulimit command to raise the stack size limit (the csh equivalent is 'limit stack'). For example, # ulimit -s 32768. Once raised the limit applies to the current process and any children of that process.

    Alternately, you can use the -s compiler option to program storage from the stack to the heap.

  • Mac OS X Intel - How do I upgrade a trial license to a purchased license without re-installing?

    To replace a trial license with a purchased license:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually /Applications/AbsoftXXXX where XXXX represents the product version number)

    2) Delete the license string that follows the word "LICENSE:"

    3) Type in your new license string without the dashes.

    4) Save the license file in plain text format.

    5) Restart your computer.

  • Mac OS X Intel - How do I use the IMSL libraries?

    NOTE: The IMSL library is built with all external symbols folded to lower case with trailing underscores.

    If you are building your program with the Absoft Developer Tools Interface, simply select Default Tool Options from the Project Menu, choose General options, and click the IMSL check box. The Absoft Developer Tools Interface will add all of the necessary compiler options and libraries.

    To use the library from the command line, the necessary environment variables were established when the library was installed. Refer to the following document for complete details on using the library from the command line:

    /opt/CTT6.0/notes/f90/absoft_32/quickstart

    Or:

    /opt/CTT6.0/notes/f90/absoft_64/quickstart

  • Mac OS X Intel - The Fx3 Graphical Debugger is not working - How do I fix this?

    Fx3 requires the use of the Bash shell on a Mac. To set your terminal.app (/Applications/utilities/) to use the bash shell, do the following:

    • On Tiger (OS X 10.4):
      Open a terminal and go to Terminal -> Preferences. Select "Execute this command (specify complete path):", put in "/bin/bash". Close the window and close the terminal.

    • On Leopard (OS X 10.5):
      Open a terminal and go to Terminal -> Preferences. Go to "Shells open with:" Select "command (complete path):". In the text box type "/bin/bash" press enter and then close the window. Close and restart the terminal.

  • Mac OS X PPC - After installation, I receive the message "Unable to obtain license: license server not found" or "Unable to obtain license: license not found." How do I fix this?

    Single User Licenses:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually /Applications/AbsoftXXXX where XXXX represents the product version number)

    2) If your license file does not contain a line which reads "SERVER: 127.0.0.1", add this line at the top of the file.

    3) Verify that there is a line which begins with "LICENSE:" If there is a line which begins with "PRO:", replace "PRO:" with "LICENSE:"

    4) Verify that the string following "LICENSE:" does not contain any dashes ("-").

    5) If you made any changes, save the license file in plain text format.

    6) Reboot your computer and test.

    7) If you still receive the error, send an email to support@absoft.com which includes your operating system version (OS X 10.4 Tiger or OS X 10.5 Leopard) and hardware platform. 

    * Please attach your license.dat file as well as the file named "absoft_release" from the Absoft installation folder.

    Multiple User Licenses:

    1) Send an email to support@absoft.com which includes the operating system and hardware information for the system on which you are running the Absoft license server and for the client which is unable to obtain a license.

    *Attach the license.dat files from the server and from the client which is unable to obtain a license.

  • Mac OS X PPC - Are Unix and Vax subroutines such as DATE, TIME, GETARG, IARGC, etc, supplied with the Absoft compiler?

    Complete Unix and Vax compatibility libraries are provided with the Absoft compiler. They are documented in the Absoft manual "SupportLibrary.pdf" in the Absoft documentation directory. Several methods of accessing the library are available. The easiest is with the Absoft Developer Tools Interface. From the Project menu, select Default Tool Options. In the General options section, check the Unix Library or the Vax Library check box.

    Fortran 90/95 modules are also provided for these libraries. Simply add a USE statement to use program. 

    For example:

    use vax_library
    character*20 thedate
    call date(thedate)
    print *,thedate
    end

    use unix_library
    character*24 tim
    tim = ctime(5)
    write (*,*) tim
    end

  • Mac OS X PPC - Can I run Pro Fortran 9.5 on Intel Macs?

    Yes. Pro Fortran 9.5 works on Intel Macs and can produce 32 bit PowerPC programs that will execute on Intel Macs using Apple's emulation technology.

    Due to limitations of the emulation system, 64 bit Power PC applications cannot be executed and the Power PC Fx3 debugger cannot be used on Intel based hardware for either 32 or 64 bit applications.

  • Mac OS X PPC - Do I need to uninstall my previous Absoft compiler before installing my upgrade?

    You can address more than 2 GB of memory if you are using Pro Fortran on a OS X 10.4 system with a 64-bit processor (G5). You need to use the '-m64' switch to do this. There are two limitations:

    1. Due to a bug in the Apple assembler you can only address more than 2GB of memory if you are using dynamic allocation (Fortran 90 allocate)

    2. Common blocks still have a 2GB limitation.

  • Mac OS X PPC - How can I modify the default behaviour of the Absoft runtime library?

    The runtime library checks for an environment variable named ABSOFT_RT_FLAGS on entry to the first I/O statement in a program.

    The following switches can be specified using this variable:

    -defaultcarriage:
    Causes the units preconnected to standard output to interperet carriage control characters as if they had been connected with ACTION='PRINT'.

    -fileprompt: 
    Causes the library to prompt the user for a filename when it implicitly opens a file as the result of I/O to an unconnected unit number. By default, the library creates a filename based on the unit number.

    -vaxnames: 
    Causes the library to use 'vax style' names (FORnnn.DAT) when creating a filename as the result of I/O to an unconnected unit number.

    -unixnames: 
    Causes the library to use 'unix style' names (fort.nnn) when creating a filename as the result of I/O to an unconnected unit number.

    -bigendian: 
    Causes the library to interpret all unformatted files using big endian byte ordering.

    -littleendian: 
    Causes the library to interpret all unformatted files using little endian byte ordering.

    -noleadzero: 
    Causes the library to surpress the printing of leading zeroes when processing an Fw.d edit descriptor. This only affects the limited number of cases where the ANSI standard makes printing of a leading zero implementation defined. 

    -reclen32: 
    Causes the library to interpret the value specified for RECL= in an OPEN statement as 32-bit words instead of bytes. 

    -f90nlexts:
    Allows f90 namelist reads to accept non-standard syntax for array elements. Without this flag, the following input results in a runtime error:

    $ONE

    A(1)=1,2,3,4

    $END

    When -f90nlexts is set, the values are assigned to the first four elements of A.

    -connectunit9
    Causes UNIT 9 to be preconnected to standard input and output.

    -maceol
    Formatted sequential files are in Classic Macintosh format where each record ends with a carriage return.

    -doseol
    Formatted sequential files are in Windows format where each record ends with a carriage return followed by a line feed.

    -unixeol
    Formatted sequential files are in Unix format where each record ends with a line feed.

    -hex_uppercase
    Data written with the Z edit descriptor will use upper case characters for A-F.

    To set ABSOFT_RT_FLAGS using bash, open the terminal and enter:

    export ABSOFT_RT_FLAGS=-fileprompt

    To set ABSOFT_RT_FLAGS using tcsh, open the terminal and enter:

    setenv ABSOFT_RT_FLAGS -fileprompt

    *Note: MRWE applications must be launched from the command prompt so that the ABSOFT_RT_FLAGS will be used.

  • Mac OS X PPC - How do I install my Absoft compiler?

    Use the following instructions to install the product.

    STEP 1:

    After inserting the Absoft Pro Fortran CD-ROM into your CD Drive, you will see an icon labeled 'AbsoftProFortran95'. This is the installer you need to run.

    To start the installation, double click on the icon. You will be prompted for your administrator name and password. After entering this information the installation process will begin and you will be prompted to enter your name, company name, and the serial number of your Pro Fortran software. 

    You must enter your name and the serial number to complete the installation.

    Your Absoft Pro Fortran serial number can be found on the inside front cover of the CD case or in your delivery email.

    STEP 2:

    Absoft Pro Fortran relies on several components from the Xcode Tools package. Before using Pro Fortran, please make sure you have Xcode installed. Depending on the version of OS X you are using, there are a few possible locations for this package:

    A) Check your OS X distribution media; you may already have an Xcode CD

    B) Check for an Xcode package in the Installers folder located in Applications

    C) You may download Xcode from http://www.apple.com

    STEP 3:

    If you wish to run Pro Fortran from the command line, you will need to modify your shell startup script to set up some environment variables. If you are using bash, add the following lines to the .bash_profile in your home directory: (If you don't have a .bash_profile, create one with these lines in it)

    export ABSOFT=/Applications/Absoft9.5
    export PATH=$ABSOFT/bin:$PATH

    If you are using a different shell, refer to that shell's documentation for
    the correct syntax for setting and exporting environment variables.

    You will need to restart the Terminal Application before these changes will take effect.

    Please see the document 'Pro Fortran 9.5 Release Notes.pdf' for additional information about Pro Fortran.

  • Mac OS X PPC - How do I link to libraries?

    All libraries supplied with the Absoft compiler (such as LAPACK) are built with all external symbols folded to lower case with trailing underscores. The required options for linking to these libraries are:

    f90: -YEXT_NAMES=LCS, -YEXT_SFX=_

    f77: -f -N15

    To link with other third party libraries, it is necessary to determine how the external symbol names are presented (case folding and decoration) and use the appropriate compiler options.

  • Mac OS X PPC - How do I solve stack overflow problems?

    The default for Pro Fortran is an 8 megabyte stack. Use the bash ulimit command to raise the stack size limit (the csh equivalent is 'limit stack'). For example, # ulimit -s 32768. Once raised the limit applies to the current process and any children of that process.

    Alternately, you can use the -s compiler option to program storage from the stack to the heap.

  • Mac OS X PPC - How do I upgrade a trial license to a purchased license without re-installing?

    To replace a trial license with a purchased license:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually /Applications/AbsoftXXXX where XXXX represents the product version number)

    2) Delete the license string that follows the word "LICENSE:"

    3) Type in your new license string without the dashes.

    4) Save the license file in plain text format.

    5) Restart your computer.

  • Mac OS X PPC - How do I use the IMSL libraries?

    NOTE: The IMSL library is built with all external symbols folded to lower case with trailing underscores.

    If you are building your program with the Absoft Developer Tools Interface, simply select Set Project Options from the Configure Menu, choose the Plug-ins tab, and click the IMSL check box. The Absoft Developer Tools Interface will add all of the necessary compiler options and libraries.

    To use the library from the command line, the necessary environment variables were established when the library was installed. Refer to the following document for complete details on using the library from the command line:

    /opt/CTT6.0/notes/f90/absoft_32/quickstart

    Or:

    /opt/CTT6.0/notes/f90/absoft_64/quickstart

  • Mac OS X PPC - The Fx3 Graphical Debugger is not working - How do I fix this?

    Fx3 requires the use of the Bash shell on a Mac. To set your terminal.app (/Applications/utilities/) to use the bash shell, do the following:

    • On Tiger (OS X 10.4):
      Open a terminal and go to Terminal -> Preferences. Select "Execute this command (specify complete path):", put in "/bin/bash". Close the window and close the terminal.

    • On Leopard (OS X 10.5):
      Open a terminal and go to Terminal -> Preferences. Go to "Shells open with:" Select "command (complete path):". In the text box type "/bin/bash" press enter and then close the window. Close and restart the terminal.

  • Windows - After installation, I receive the message "Unable to obtain license: license server not found" or "Unable to obtain license: license not found." How do I fix this?

    Single User Licenses:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually C:\AbsoftXXXX where XXXX represents the product version number)

    2) If your license file does not contain a line which reads "SERVER: 127.0.0.1", add this line at the top of the file.

    3) Verify that there is a line which begins with "LICENSE:" If there is a line which begins with "PRO:", replace "PRO:" with "LICENSE:"

    4) Verify that the string following "LICENSE:" does not contain any dashes ("-").

    5) If you made any changes, save the license file in plain text format.

    6) Reboot your computer and test.

    7) If you still receive the error, send an email to support@absoft.com which includes your operating system version (Windows 2000, Windows XP, Windows Vista), hardware type (32 or 64 bit) and attach your license.dat file as well as the file named "absoft_release" from the Absoft installation folder.

    Multiple User Licenses:

    1) Send an email to support@absoft.com which includes the operating system and hardware information for the system on which you are running the Absoft license server and for the client which is unable to obtain a license. 

    *Attach the license.dat files from the server and from the client which is unable to obtain a license.

  • Windows - Are Unix and Vax subroutines such as DATE, TIME, GETARG, IARGC, etc, supplied with the Absoft compiler?

    Complete Unix and Vax compatibility libraries are provided with the Absoft compiler. They are documented in the Absoft manual "SupportLibrary.pdf" in the Absoft documentation directory. Several methods of accessing the library are available. The easiest is with the Absoft Developer Tools Interface. From the Project menu, select Default Tool Options. In the General options section, check the Unix Library or the Vax Library check box.

    Fortran 90/95 modules are also provided for these libraries. Simply add a USE statement to use program. 

    For example:

    use vax_library
    character*20 thedate
    call date(thedate)
    print *,thedate
    end

    use unix_library
    character*24 tim
    tim = ctime(5)
    write (*,*) tim
    end

  • Can I use Open MPI & MPICH with Absoft Fortran compilers?

    Yes, please visit the Absoft Resources page (www.absoft.com/Products/Compilers/Fortran/Linux/fortran95/MPich_Instructions.html) for the MPI configurations supported by Absoft, as well as build instructions for Open MPI & MPICH for Absoft compilers.

  • How Do I Find My License Number?

    Your Absoft Serial Number (license key) can be found in several places, such as:

    • On the outside of the Absoft software box

    • The inside front cover of your printed user guide

    • The back of the CD sleeve

    • On your registration form

    • If you received your software via download, your license number is included in the delivery email 

    If you do not have any of the above, you can also locate your serial number from your license.dat file 
    • For Windows, Mac & x86/x86_64 Linux: The license.dat file is located in the Absoft folder.

    • For Linux PPC: The license.dat file is located in the clm_ibm folder.

  • Windows - How do I install my Absoft compiler?

    Use the following instructions to install the product.

    For downloaded compilers:

    After downloading the compiler, double click the .exe which will launch the installer, you will be prompted to enter your name, company name, and your serial number.

    You must enter your name and the serial number to complete the installation.

    Your Absoft Pro Fortran serial number can be found in the delivery email.

    If you have the Absoft CD:

    Insert the Absoft Pro Fortran CD-ROM into your CD Drive. Unless you have disabled the Windows 'Auto Play' feature, the installation program will launch automatically. If it does not run, select Run… from the Start Menu and enter:

    d:\setup.exe

    and click OK to begin installation.

    After launching the installer, you will be prompted to enter your name, company name, and the serial number of your Pro Fortran software. You must enter your name and the 19 character serial number to complete the installation.

    Your Absoft Pro Fortran serial number can be found on the inside front cover of the CD case.

  • Windows - How do I pass an array from VB to a DLL?

    Refer to your Microsoft VisualBasic Programmer's Guidepage 652. VB passes entire arrays using OLE Automation argument protocols. Absoft F77/F90/C/C++ expect CDECL arguments. The VB manual section explains how to pass the address of the first argument of the array. 

    Basically:

    Declare ... lParam as Any

    Dim array(100)

    Call DLL(array(0))

  • Windows -How do I link to libraries?

    All libraries supplied with the Absoft compiler (such as LAPACK) are built with all external symbols folded to lower case with trailing underscores. The required options for linking to these libraries are: 

    f90: -YEXT_NAMES=LCS, -YEXT_SFX=_ 

    f77: -f -N15 

    NOTE: These are default options for Pro Fortran V10.1. 

    To link with other third party libraries, it is necessary to determine how the external symbol names are presented (case folding and decoration) and use the appropriate compiler options.

  • Windows - How do I solve stack overflow problems?

    The default for Pro Fortran is a 1 megabyte stack. The option -stack:n can be used to increase the stack (where n is the amount of stack required). For example, -stack: 0x2000000 will allocate approximate 32 megabytes to the stack.

    Alternately, you can use the -s compiler option to program storage from the stack to the heap.

  • Windows - How do I upgrade a trial license to a purchased license without re-installing?

    To replace a trial license with a purchased license:

    1) Using a text editor, open the file named license.dat located in the Absoft installation folder (usually C:\AbsoftXXX where XXX represents the product version number)

    2) Delete the license string that follows the word "LICENSE:"

    3) Type in your new license string without the dashes.

    4) Save the license file in plain text format. 

    5) Restart your computer.

  • Windows - How do I use the IMSL libraries?

    NOTE: The IMSL library is built with all external symbols folded to lower case with trailing underscores. 

    If you are building your program with the Absoft Developer Tools Interface, simply select Default Tool Options from the Project Menu, choose General options, and click the IMSL check box. The Absoft Developer Tools Interface will add all of the necessary compiler options and libraries. 

    To use the library from the command line, the necessary environment variables were established when the library was installed. Refer to the following document for complete details on using the library from the command line: 

    C:\Absoft10.1\CTT6.0\Notes\f90\Absoft_32\Quickstart.txt 

    Or: 

    C:\Absoft10.1\CTT6.0\Notes\f90\Absoft_64\Quickstart.txt

  • Supported OS Distributions

    Windows 32/64-bit: 

    • Win2K - Vista

    Mac 32/64-bit, PPC or Intel Based: 

    • Tiger - Leopard

    Linux x86:
    • Red Hat Enterprise Linux 3.0 or later

    • SuSE 8.1 or later

    • Mandrake 8.2 or later

    • Fedora Core 1 or later

    • Ubuntu


    Linux x86_64:
    • Red Hat Enterprise Linux 3.0 or later

    • SuSE 8.0 or later

    • Ubuntu

  • What Version Do I Have?

    The Absoft version number is found on:

    • The front of your product CD

    • The Absoft compiler start-up screen

    • The absoft_release file in the Absoft Directory on your hard-drive

  • Windows - How can I modify the default behaviour of the Absoft runtime library?

    The runtime library checks for an environment variable named ABSOFT_RT_FLAGS on entry to the first I/O statement in a program.

    The following switches can be specified using this variable:

    -defaultcarriage:
    Causes the units preconnected to standard output to interperet carriage control characters as if they had been connected with ACTION='PRINT'.

    -fileprompt: 
    Causes the library to prompt the user for a filename when it implicitly opens a file as the result of I/O to an unconnected unit number. By default, the library creates a filename based on the unit number.

    -vaxnames: 
    Causes the library to use 'vax style' names (FORnnn.DAT) when creating a filename as the result of I/O to an unconnected unit number.

    -unixnames: 
    Causes the library to use 'unix style' names (fort.nnn) when creating a filename as the result of I/O to an unconnected unit number.

    -bigendian: 
    Causes the library to interpret all unformatted files using big endian byte ordering.

    -littleendian: 
    Causes the library to interpret all unformatted files using little endian byte ordering.

    -noleadzero: 
    Causes the library to surpress the printing of leading zeroes when processing an Fw.d edit descriptor. This only affects the limited number of cases where the ANSI standard makes printing of a leading zero implementation defined. 

    -reclen32: 
    Causes the library to interpret the value specified for RECL= in an OPEN statement as 32-bit words instead of bytes. 

    -f90nlexts:
    Allows f90 namelist reads to accept non-standard syntax for array elements. Without this flag, the following input results in a runtime error:

    $ONE

    A(1)=1,2,3,4

    $END

    When -f90nlexts is set, the values are assigned to the first four elements of A.

    -connectunit9
    Causes UNIT 9 to be preconnected to standard input and output.

    -maceol
    Formatted sequential files are in Classic Macintosh format where each record ends with a carriage return.

    -doseol
    Formatted sequential files are in Windows format where each record ends with a carriage return followed by a line feed.

    -unixeol
    Formatted sequential files are in Unix format where each record ends with a line feed.

    -hex_uppercase
    Data written with the Z edit descriptor will use upper case characters for A-F.

    To set ABSOFT_RT_FLAGS open a command prompt window and enter:

    set ABSOFT_RT_FLAGS=-switch

    *Note: MRWE applications must be launched from the command prompt so that the ABSOFT_RT_FLAGS will be used.