Microsoft Fortran Powerstation 40 Serial

Microsoft Fortran Powerstation 40 Serial 3,7/5 9575 votes

Hi, I've installed Intel Visual Fortran Pro and am working on a visual studio project that has some C++ code that calls a few functions from fortran libraries. Macdrive 9 serial tpb pc. When I build the project initially it looks for LIBC.lib, which it can't open.

Download microsoft fortran 4.0 for free. Development Tools downloads - Microsoft Fortran by Microsoft and many more programs are available for instant and free download.

I've found the files on an old Powerstation 4.0 disc. So after installing the software on my computer, and point to the directory with the necessary libraries in it, i receive the second set of errors. (both sets of errors are pasted below) Is there some way to set a default library to override other libraries in case functions are multiply defined? Thanks, Kevin ====================1st SET OF ERRORS=================== 1>------ Build started: Project: adsa1, Configuration: Debug Win32 ------ 1>Linking. 1>LINK: fatal error LNK1104: cannot open file 'LIBC.lib' 1>Build log was saved at 'file://j: My Documents B02 - 20081227 UH Work - Zuo AdsaInterf 3.0 source Debug BuildLog.htm' 1>adsa1 - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped ========== ************************************************************************* ====================2nd SET OF ERRORS=================== 1>------ Build started: Project: adsa1, Configuration: Debug Win32 ------ 1>Linking. On Windows, compilers usually add a set of 'directives' to the object file which tells the linker to pull in certain libraries.

This is done so that you don't have to manually list the libraries. The library you are using would appear to have been built by or at least for Microsoft Fortran PowerStation, as some of the libraries you list are for that product. You cannot mix these objects with Intel Fortran. Libc.lib is a Microsoft Visual C++ library that is not thread-safe. It was discontinued as of VS2005. While many of the symbols in libc.lib can be fulfilled by libcmt.lib (the thread-safe variant), the C/C++ compiler actually generates different code if you're using the thread-safe version (/MT is the switch), so you'll get link errors regardless.

In the end, you cannot use this library with Intel Fortran - it requires Microsoft Fortran PowerStation (taken off the market 12 years ago). On Windows, compilers usually add a set of 'directives' to the object file which tells the linker to pull in certain libraries. This is done so that you don't have to manually list the libraries.

The library you are using would appear to have been built by or at least for Microsoft Fortran PowerStation, as some of the libraries you list are for that product. You cannot mix these objects with Intel Fortran. Libc.lib is a Microsoft Visual C++ library that is not thread-safe. It was discontinued as of VS2005.

While many of the symbols in libc.lib can be fulfilled by libcmt.lib (the thread-safe variant), the C/C++ compiler actually generates different code if you're using the thread-safe version (/MT is the switch), so you'll get link errors regardless. In the end, you cannot use this library with Intel Fortran - it requires Microsoft Fortran PowerStation (taken off the market 12 years ago).

Thanks for the explanation steve. Is there a way in VS2008 to default so that libcmtd.lib's definitions take precedence and all other library's function/variable definitions are ignored (if they happen to be duplicates)? Thanks Kevin. Ah, Well I don't want to really exclude/ignore the entire library. Just the functions/variables that are defined elsewhere. Does the /force:multiple option do this?

Thx for all the help Steve! Kevin Hi I tried the /force:multiple option and it did what it was supposed to, ignoring one of the redundant definitions.

It did, however result in the following error and the.exe generated did not run/open:.Debug/adsa1.exe: warning LNK4088: image being generated due to /FORCE option; image may not run What does this mean? Would a dynamic linking to the MFC and C runtime libraries solve my problem? It was suggested to me but i'm not quite sure how to do it in vs2008. Kevin, If you have the sources to build the library in PS, why not do it using Intel? Hi Dave Actually I only have the.lib files.

I tried to build a.dll using Intel VF, but VS2008 said I had a corrupted dll file and wouldnt compile. I included all 6 fortran calculation libraries: dverk.lib lapack.lib minpack1.lib blas.lib colsys.lib libtiff.lib and the powerstation.lib files that the calculation libraries are dependent on: console.lib libc.lib libf.lib portlib.lib Unfortunately, I do not have the source code for the 6 calculation libraries. At least some of these libraries possibly have alternatives or available sources. Dverk is probably on netlib. Lapack and blas at least are probably in the math library available with IVF.