Platform: All Problem Details: OS Version: Any Product Version: Any Date: 22-Sep-97 Q. Where can I find IMSL documentation. A. The documentation for the IMSL libraries (7 volume set) may be purchased separately, or you can find it on line at: http://www.vni.com/products/imsl/alphabetized_functions.html |
Platform: All Problem Details: OS Version: Any Product Version: Any Date: 22-Sep-97 Q. I'm having problems using the IMSL functions. The linker reports unresolved references for any function I try to use. A. You must include the IMSL library: Windows: imsl.lib Macintosh: "{AbsoftLibraries}"imsl.lib Linux: libimsl.a as an argument to the linker. On Windows and Macintosh, the libraries have been compiled with the fold to lower case option (-f) enabled. On Linux, they have been compiled with the fold to upper case option (-N109) enabled. It will be necessary either to: a) use a compiler case folding option b) spell the library names in the correct case c) use a linker alias file (not available on Linux) |
Platform: All Problem Details: OS Version: Any Product Version: Fortran77 Date: 24-Sep-97 Q. Does FORTRAN 77 support the -r8 flag? A. Use the -N113 compiler option. The -N2 option forces all intrinsic functions to be performed in DOUBLE PRECISION. |
Platform: All Problem Details: OS Version: Any Product Version: Any Date: 02-Oct-97 Q. I have a file which "uses" a precompiled by module containing a function used by the main file. When I try to compile the main it says there is an unresolved reference. A. Your module contains executable code. Precompiling it created both a module file and an object file. Present the object file to the linker and the reference will be resolved. If you're compiling from the command line, simply add the object file on the compiler invocation line. |
Platform: Macintosh Problem Details: OS Version: any Product Version: any Date: 22-Oct-97 Q. Apparently the compiler considers the variable NORMX as integer even though I explicitly typed it as: real normx Please fix the compilers and send me the patch. A. There is no need to provide a patch for the compiler. The FORTRAN 77 compiler is case sensitive. You can use either of the two following options to disable case sensitivity: -f fold to lower case (User Guide pp. 5-17, 6-1, I-1) -N109 fold to upper case (User Guide pp. 5-17, I-2) Caution: The use of either option will make it impossible to communicate directly with the Macintosh API. |
Platform: Macintosh Problem Details: OS Version: any Product Version: any Date: 03-Dec-97 Q. How do I allocate memory to a FORTRAN program? A. How you specify the size of the memory partition of a FORTRAN program depends on whether the program is designed to run as an MPW tool or a Macintosh desktop application. If it is to run within MPW as a tool, then the only memory available to it is that allocated to MPW itself. In other words, the program and its memory requirement must fit entirely within MPW. Use Get Info on the MPW Shell icon to increase the size of MPW parition. If the program is designed as a stand-alone Macintosh desktop application, then its memory allocation is specified by using Get Info on the program's icon. |
Platform: Macintosh Problem Details: OS Version: any Product Version: any Date: 05-Feb-98 Q. I am trying to compile a program using MPW and when I run the compiler or linker and I receive this message: "not enough room in heap zone (OS error -108)" I have plenty of memory on my system, why doesn't MPW use it? A. MPW must have all of the memory it will use preallocated to it. The default allocation is 16 MB. To increase it (and we recommend 32 MB), first exit MPW. Then, open the MPW folder and click the mouse button once on the MPW Shell icon. (You want to select it, but not open it). Choose "Get Info" from the "File" menu which will open a dialog box, allowing you to change MPW's memory allocation. |
Platform: All Problem Details: OS Version: Any Product Version: Pro Fortran 6.0 and later Date: 04-Sep-98 Q. How can I modify the default behavior of the Absoft runtime library? A. Starting with Absoft Pro Fortran 6.0 and Absoft Fortran SDK 4.5, 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. Note: the leading minus sign is required for each switch and multiple switches must be separated by one or more spaces. |
Platform: Macintosh Problem Details: OS Version: any Product Version: any Date: 23-Dec-98 Q. After upgrading my MacOS I have noticed that the F90 compiler can not report compile-time errors. Instead I get a message like this: "cft90 INTERNAL: Cannot retrieve message 3 from the message system" Something must be set-up improperly. Any advice? A. There are two files which contain error messages: tmod and cf90. These files are maintained in {SystemFolder}Preferences:Absoft so if you replace you Mac OS these files will not exist. If you no longer have these files, you must reinstall your Absoft product in order for your f90 compiler to display error messages. |
Platform: All Problem Details: OS Version: any Product Version: any Date: 14-Jan-99 Q. Does Absoft Fortran pass the lengths of strings like most Unix Fortran compilers I've used? A. Yes, string lengths are passed as extra arguments (by value) at the end of the formal argument list: C:\Absoft60>type main.c #include <string.h> void Fcode(char *, int, double *, int); int main() { char string[13] = {"hello, world"}; int i = 1; double d = 2.0; Fcode(string, i, &d, strlen(string)); return 0; } C:\Absoft60>acc -c -A main.c Absoft C/C++ Compiler 1.3, Copyright (c) 1994-1997, Absoft Corp. C:\Absoft60>type fcode.f subroutine Fcode(string, i, d) character*(*) string integer i value i double precision d print *, string, i, d, len(string) end C:\Absoft60>f77 -o main.exe main.obj fcode.f FORTRAN 77 Compiler 4.5, Copyright (c) 1987 - 1998, Absoft Corp. C:\Absoft60>main hello, world 1 2.00000000000000 12 C:\Absoft60> |
Platform: Macintosh Problem Details: OS Version: any Product Version: any Date: 03-Feb-99 Q. Is there a way to read an ASCII tab character, CHAR(9), from a file? A. In Pro Fortran 5.0, tabs read from formatted files are expanded modulo 8. In Pro Fortran 6.0 and later tabs read from formatted files are expanded modulo TAB where TAB is an MPW environment variable. If TAB is not set, tabs are expanded modulo 8. If TAB is set to 0, the tab is passed unmolested to the application. There is no way in either version to affect the expansion of tabs in an MRWE application unless you are using version 6.2 or later. |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.0 Date: 08-Mar-99 Q. How do I turn off text colorization in MPW? A. Edit the file "MPW:Startup Items:UserStartup*Absoft" and insert the following line anywhere in the file: Set -e AllowColorizing 0 Save your changes and restart MPW. |
Platform: Macintosh Problem Details: OS Version: any Product Version: any Date: 01-Jun-99 Q. How do I use the Macintosh Toolbox API? A. Using the Macintosh Toolbox API is beyond the scope of Absoft technical support. For more information on the Macintosh Toolbox API see Inside Macintosh - Macintosh Toolbox Essentials by Apple Computer, Inc. http://www.apple.com/developer/ |
Platform: Macintosh Problem Details: OS Version: Any Product Version: Any Date: 16-Jul-99 Q. I am trying to write a large array as one record and when using the -N3 compiler option I get this run time error: ? FORTRAN Runtime Error: ? Buffer allocation failed ? WRITE(UNIT=3,... A. The -N3 option instructs the compiler to read/write unformatted sequential access files with record length information embedded in the record. This places a 32-bit integer at the beginning and the end of each record which allows the runtime library to skip and backspace these records. Without the length information that would be impossible. However, your write statements try to write this entire array as one record. With the -N3 option we have to allocate enough memory in one contiguous chunk to create this record so that the length information can be inserted at the beginning and the end. The allocation of this buffer is what failed. When the -N3 option is not specified, I/O transfers are performed using much smaller (4096 byte) buffers since the data is pure binary with no record length information. If you receive this error on the Macintosh, then increase the memory application size. |
Platform: Macintosh Problem Details: OS Version: any Product Version: any Date: 22-Jul-99 Q. When I make changes to my makefile such as new compiler options, my application does not rebuild unless I delete the old object files manually. A. Make the makefile a dependency of your target by deleting the "#" character in line four in the makefile. |
Platform: Macintosh Problem Details: OS Version: Mac Product Version: any Date: 05-Aug-99 Q. I try to open the MPW shell and I get these messages: Command project menu was not found Execution of Startup terminated Or, I do a set command from the MPW Worksheet and I get the message: ### MPW Shell- 's must occur in pairs. A. Some probable causes for this behavior is caused by including spaces, apostrophes or dashes in the name of your hard drive or path names and trying to work in MPW. Instead of a dash, use an underscore. For example: HD_A |
Platform: Macintosh Problem Details: OS Version: OS-9 Product Version: any Date: 20-Oct-99 Q. I just upgraded to Mac OS version 9 and when I exit the MPW shell I get this error message: "The application "MPW Shell has unexpectedly quit, because an update to this software is required for compatibility with the improved Mac OS file system. You should save your work in other open applications and restart the computer." A. The Shell supplied with MPW V3.4.3 and V3.4.4 is not compatible with the StdClib built into Mac OS-9. For more information, please refer to this Apple Computer web page: http://developer.apple.com/macos/macos9.html The MPW Shell version 3.5 is required for Mac OS-9. You can download it from this Apple FTP site: ftp://ftp.apple.com/developer/Tool_Chest/Core_Mac_OS_Tools/MPW_etc./MPW-GM/MPW/ And download the file: MPW_Shell.sit.hqx And put the new MPW shell in the MPW folder that is installed with Absoft Pro Fortran. You should also update the StdClib shared library supplied in the MPW:Libraries:SharedLibraries folder. Go to: ftp://ftp.apple.com/developer/Tool_Chest/Core_Mac_OS_Tools/MPW_etc./MPW-GM/Interfaces&Libraries/ And download the files: RuntimeLibraries.sit.hqx Libraries.sit.hqx In RuntimeLibraries, in the folder Power Macintosh Additions, Mac OS 7.6 or later, you will find the StdClib that should go into: MPW:Libraries:SharedLibraries And in Libraries, PPCLibraries you will find the files: StdCRuntime.o PPCStdClib.o Put them in MPW:Libraries:PPCLibraries You must also increase the MPW partition size and the stack. You must also increase the MPW partition size and the stack. The partition should be at least 16 MB and preferably 32 MB. Use Get Info on the MPW Shell icon to set it. Use the MPW Shell command SetShellSize to set the stack size: SetShellSize -s 4096k |
Platform: All Problem Details: OS Version: Any Product Version: Any Date: 17-Dec-99 Q. I get the error message: "adjustable array is not a dummy argument" A. The most common cause of this is: subroutine some_name(a,b,n) real A(N), B(N) The FORTRAN 77 compiler is case sensitive by default. The easiest way to solve this type of problem is use a case folding option: -f or -N109. |
Platform: Macintosh Problem Details: OS Version: Any Product Version: Any Date: 20-Dec-99 Q. I have a problem printing from the MPW editor to my EPSON printers. My new Epson connected to my Mac won't print any MPW shell documents like program listings, active window files, etc. The message it sends is "essential print resource missing" or the number of copies to be printed appears to be a random number of both signs. When it pops up as a negative number only one copy is printed. Normally it comes up as thousands of copies and the printing must be forced to stop. The MPW shell works fine with other printers like Laser Writers and HP printers. A. EPSON printers need the print dialog box in order to control the number of copies printed. Type this command in the MPW worksheet and hit enter: Set PrintOptions "-h -dialog" index |
Platform: Macintosh Problem Details: OS Version: Any Product Version: Any Date: 04-Feb-00 Q. I'm trying to use the -N9 option (Frequent Command-Period checks) with my C program, but it doesn't seem to work. A. For C programs, it is necessary to call the "mrwe_install_timer()" at the beginning of your main function. For example: int main() { void mrwe_install_timer(); mrwe_install_timer(); Note: If you are using ProFortran 6.0 or earlier, you must also specify this option: -N103, which can only be done in a makefile or from the command line. |
Platform: Macintosh Problem Details: OS Version: Any Product Version: 6.2 Date: 21-Mar-00 Q. When using an F90 source file, ACM improperly adds -Yaltivec to the makefile like this: f90_ppc_opts = "-Yaltivec Resulting in a make error message. A. Go to the Absoft download site install Service Pack: http://www.absoft.com/download/os9mac6.2downloads.html |
Platform: Macintosh Problem Details: OS Version: Any Product Version: 6.2 Date: 21-Mar-00 Q. I can't get the VMS (or UNIX) libraries to link. A. The libraries contain three entry points for each function. One in all upper case, one in all upper case with a trailing underscore, and one in all lower case with a trailing underscore: DATE DATE_ date_ Be sure that your spelling matches one of these. Use the fold to upper case compiler option (-N109) to simplify using them with the Fortran 90 compiler as well as the FORTRAN 77 compiler. To specify the library simply add it as source file on the compiler invocation line (it is a source file to the linker). They are in "MPW:Libraries:AbsoftLibraries" as "vmslib.o" and "unixlib.o". You can use the shell variable "(AbsoftLibraries)" to specify the path from the MPW shell For example: test.f: character*40 argument n = IARGC () do i=1,n call GETARG(i,argument) end do end f77 -tool test.f {AbsoftLibraries}unixlib.o |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 23-Mar-00 Q. I tried to compile the SuperPlot-Lite examples, but the include file and library appears to be missing. A. They were accidently left off the CD-ROM. You can download them from here: http://www.absoft.com/download/os9mac6.2downloads.html |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 24-Mar-00 Q. When compiling a program that uses the MIG graphics library, either by checking the "Uses graphics" box in the Compiler Commando interface or by adding the library directly to a build or command line, I get following error: # link error: undefined symbol - .ldtox80 # first ref in - HD:MPW:Libraries:AbsoftLibraries:mig.o A. The MIG library needs one additional library when it is linked to your application. This is the Apple library: "{SharedLibraries}"MathLib Add this library to your command line or makefile. If you are using the Compiler Commando interface, use the "Library File(s)..." button and then navigate to ":MPW:Libraries:SharedLibraries". |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 27-Mar-00 Q. Which Absoft libraries are optimized for the G4's Velocity Engine? A. See http://www.absoft.com/Products/Libraries/altivec.html for more information. |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 06-Apr-00 Q. Why do I get an "The application MPW Shell could not be opened because StdCLib could not be found." error after installing ProFortran 6.2? A. The MPW shell shipped with Pro Fortran 6.2 requires a new version of StdCLib for systems which are running pre OS9 versions of MacOS. This library is available for download from the Absoft site at the following location: http://www.absoft.com/download/os9mac6.2downloads.html If you want all of the latest libraries including StdCLib3.5, they are available from the Apple ftp site at: ftp://ftp.apple.com/developer/Tool_Chest/Core_Mac_OS_Tools/MPW_etc./MPW-GM After downloading and unpacking, simply drag StdCLib to your system folder. Your Macintosh will automatically move it to the Extensions folder and enable it. There is no need to reboot your computer. |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 11-May-00 Q. I am having problems using IMSL version 4 or Lapack libraries on a MAC G3 with Pro Fortran 6.2. When I try to run my executable, either my program or computer crashes or the output window flashes for just a second with no output. A. The non-altivec version of the blas library inadvertently contains a few altivec routines. You must rebuild the blas.lib by following these instructions: 1) Copy Lapack folder to Hard Drive. 2) Launch MPW and Set Directory to HD:Lapack 3) Open blas_user.lib.make 4) On line 11, Uncomment the Makefile = macro dependency so it looks like the following: Makefile = "{TargetName}".make 5) On line 23, Modify the mrc_ppc macro to use ANSI C as follows: mrc_ppc = {AbsoftTools}ACC -c -A 6) Save changes to blas_user.lib.make 7) Build blas_user.lib using this makefile. Type buildprogram blas_user.lib 8) Once the build is complete replace MPW:Libraries:AbsoftLibraries:blas.lib with MPW:Libraries:AbsoftLibraries:blas_user.lib. Or you can download the blas.lib from the Absoft FTP site: ftp://ftp.absoft.com/pub/mac/profortran62/ And download the file: blas.lib.sea.hqx index |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 11-May-00 Q. I am getting unresolved function reference errors from the linker when I use the IMSL libraries in version 6.2. A. In version 6.2 we separated the blas libraries to accommodate the altivec version of the blas library. If you are compiling from the command line or a makefile add the blas.lib like this: "{AbsoftLibraries}"blas.lib If you are using the blas altivec libraries then use: "{AbsoftLibraries}"blas_altivec.lib |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 15-May-00 Q. I am trying to use the vms date routine and I receive an unresolved reference to TimeCount in vmslib.o A. You need the unix_vms_lib_update. Go to the Absoft FTP site: ftp://ftp.absoft.com/pub/mac/profortran62/ and download the file: unix_vms_lib_updates.sea.hqx index |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 06-Jun-00 Q. I am trying to compile stdfil.f and I receive the error: line 160 ## Error: invalid field. A. Change line 160 in stdfil.f from this: dirId = reply.sfFile.parId To this: dirId = reply.sfFile.parID index |
Platform: Macintosh Problem Details: OS Version: any Product Version: F77 SDK 4.6 Date: 08-Jun-00 Q. I am using the F77 SDK 4.6 Absoft Tools Commando Interface. If I add any compilers options and then click Compile, I receive a bad option error in the MPW worksheet for every option that I selected. A. There are two ways to fix this problem: 1. Go to the Absoft FTP site: http://www.absoft.com/download/os9mac6.2downloads.html And download the Service Pack: 2. In the MPW worksheet type f77 and hit OPTION ENTER. |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 12-Jun-00 Q. I am using Pro Fortran version 6.2 on a G-4 with Mac OS 9. My programs execute fine on my computer and any other Mac computer running OS-9. However, if I try to run my applications on a computer running any OS prior to OS-9 I receive the error message: stdCLib not found A. For MacOS 9, Apple made significant changes to this library in part to fix bugs and in part to support the G4. These changes were substantial enough that the library is not backward compatible. Applications that are linked against this new StdCLib will only run on systems where this library is present. Older Mac Operating Systems can use this the OS-9 version of the shell and library if the library is placed in the Extensions folder. The newer library will then replace the one built into the system at boot time. If you are using an operating system version earlier than MacOS 9 and you use the updated MPW shell and StdCLib, than any application created in the MPW environment will only run if the newer StdCLib is placed in the Extensions folder. You can get the newer StdCLib here: ftp://ftp.absoft.com/pub/mac/profortran62/StdCLib3.5.sea.hqx You only have to drop the unpacked library into your system folder. The Mac OS will know what to do with it. It is not necessary to reboot. The stdClib file in your SharedLibraties folder is not the actual Standard C Library. It is an import library that announces the functions available in the actual library. Another option for backward compatibly is to use Absoft Pro Fortran 6.0 on the G-4 with a Mac OS prior to OS 9 which will load the old StdCLib on your computer and make your applications backward compatible. |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 16-Jun-00 Q. When I use the commando interface to compile a source file with an F90 extension I get the error message: Invalid object file *.f90 Or I try to add an f90 option and I receive the error: error: bad option: -f90 A. When you installed Pro Fortran, you first installed the 'Install ProFortran' icon and then installed the 'Install Fortran SDK' icon. To solve your problem, put the MPW folder in the trash, empty the trash. Install only the 'Install ProFortran' icon. The F77 SDK will be installed as part of the Pro Fortran installation, do NOT install the 'Install Fortran SDK' icon also. index |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 16-Jun-00 Q. I am trying to use the F90 altivec optimized matmul intrinsic function but I don't see any performance gain. A. Go to the Absoft Download site And install Service Pack: http://www.absoft.com/download/os9mac6.2downloads.html |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 17-Jul-00 Q. I am trying to use the deallocate function in your f90 compiler and allocated memory is not freed when using a deallocate statement. A. You're not seeing the memory released because the f90 runtime manager is caching it. It caches all deallocated blocks so that subsequent reallocations of the same size block will occur faster. If your application requires that this be defeated, here's how: If you want to have memory returned to the system immediately you can call into the runtime library after the DEALLOCATE statement. The sample program below demonstrates the call. Please note that if any memory request is refused or fails at the system level, all cached memory is returned and the system call is repeated. program sample !DIR$ NAME (release_cache="_f90a_free_all") call release_cache() END |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 11-Aug-00 Q. I am trying to add libraries in a makefile using the Create Build Commands Libraries and selecting either UNIX, VAX/VMS, IMSL MATH/STAT or LAPACK. I receive a linker error for every routine that I try to use. It seems that the library is not linked to my project. A. Go to the Absoft download site install Service Pack: http://www.absoft.com/download/os9mac6.2downloads.html |
Platform: Macintosh Problem Details: OS Version: any Product Version: Pro Fortran v6.2 Date: 15-Aug-00 Q. I am trying to use MacMPI from http://exodus.physics.ucla.edu/appleseed/ which requires the latest version of the Shared Library OpenTransportLib. A. The Shared Library OpenTransportLib that comes with Pro Fortran version 6.2 is out of date. Go to the Absoft FTP site: ftp://ftp.absoft.com/pub/mac/profortran62/ And download the file: OpenTransportLib.hqx After unpacking the file, put it in the Libraries:SharedLibraries folder |
Platform: Macintosh Problem Details: OS Version: Any Product Version: Any Date: 25-Aug-00 Q. My program compiles fine, but every time I re-compile it I must increase the memory to the application to run it. Is there any way to automatically set the memory for my application? A. Create a makefile and add this line to the end of the # Linkage rule section: setprefs -sizemin 1000 -sizepref 1000 "{TargetName}" This will set the memory to 1000 K of memory every time you run your makefile. |
Platform: All Problem Details: OS Version: Any Product Version: Any Date: 22-Sep-00 Q. Is there an F90 compiler option that will force the compiler to consider the byte ordering of all unformatted files to either big or little endian? A. Use the F90 open statement specifier: convert ={"big_endian"|"little_endian"} For example: Open(10,file="filename",form="unformatted",convert="big_endian") Or, use the ABSOFT_RT_FLAGS as described in the technical FAQ on using the ABSOFT_RT_FLAGS environment variable which can be found here: mac6.2tfaq.html#anchor0058 |