VC++ 6.0 FORTRAN to Visual Studio 2005

[CJTalbot]

Hello,

I was wondering if anyone could help with this,I have beenasked to convert a VC++ 6.0 FORTRAN to Visual Studio 2005 but the following errors on building:

1>------ Build started: Project: SiliconCow, Configuration: Debug Win32 ------

1>Linking...(Intel C++ Environment)

1>xilink: warning: empty multi-file optimizations object list

1>xilink: executing 'link'

1>server.def : error LNK2001: unresolved external symbol DllCanUnloadNow

1>server.def : error LNK2001: unresolved external symbol DllGetClassObject

1>server.def : error LNK2001: unresolved external symbol DllRegisterServer

1>server.def : error LNK2001: unresolved external symbol DllUnregisterServer

1>.Debug/SiliconCow.lib : fatal error LNK1120: 4 unresolved externals

1>

1>Build log was saved at "file://E:NutrientManagementSystemFORTRANSiliconCowDebugBuildLog.htm"

1>SiliconCow - 5 error(s), 1 warning(s)

========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Does anyone know how to solve this problem? I have looked at multiple forums but to no avail.

Many Thanks,
Colin.

[Steven_L_Intel1]

It's not entirely clear to me what you have here, but I'm going to take some guesses.

You were using Compaq Visual Fortran in the VC++ 6.0 environment, perhaps with some C++ code as well. You have a .def file in the project. You may or may not have purchased Intel Visual Fortran. You opened your CVF project in VS2005 and let it convert it to the VC++ 2005 format, but did not take the next step and convert the Fortran project. So, when you built, all VS2005 saw was the .def file and you got linking errors. Am I close?

You need to have purchased and installed Intel Visual Fortran 9.1. Then read the document on Migrating from Compaq Visual Fortran and follow the steps for project conversion. Let me know if you have further questions.

[CJTalbot]

Hey, thanks for your email....

I havealready installed Intel Visual Fortran 9.1 and converted it via the Intel C++ Project System and get the errors posted previously.

I have had a look at the .pdf file but it does not follow correctly when using visual studio 2005. Iget to page 5 were it talks about Mixed Language Project but Idont have the option to Extract Compaq Visual Fortran Project Items.

Not sure what do from here, your advice would be greatly appreciated.

Colin.

[Steven_L_Intel1]

In VS2005, click on Help. Does the first item shown say "Intel Fortran Compiler Help" with an icon of a blue box with a white F? If not, then you have not installed the Intel Fortran Compiler integration into Visual Studio. Please rerun the compiler install, uncheck all the boxes except for the Visual Studio Integration, and try again. Pay careful attention to any error messages.

[CJTalbot]

Ok... I'm not even going to start to explain how stupid i feel at the moment... Lets just say that Intel Fortran is now installed...

It now comes up with another message:

1>------ Rebuild All started: Project: SiliconCow, Configuration: Debug Win32 ------

1>Deleting intermediate files and output files for project 'SiliconCow', configuration 'Debug|Win32'.

1>Generate Fortran include file

1>Project : error PRJ0019: A tool returned an error code

1>

1>Build log written to "file://e:FORTRANSiliconCowDebugBuildLog.htm"

1>SiliconCow build failed.

1>

========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

Just going to have a look on the web see what i can find on the web, i will let you know if i sort it.

Regards,
Colin.

[Steven_L_Intel1]

Ok, now we're getting somewhere. The contents of the build log (.htm file referenced in the build output)are important. What does it say?

[CJTalbot]

Here is the Error in the BuildLog:

------ Build started: Project: SiliconCow, Configuration: Debug|Win32 ------


Creating Type Library...

MIDL /D "_DEBUG" /nologo /env win32 /tlb "Debug/SiliconCow.tlb" "C:Documents and SettingsColin J TalbotDesktopSiliconCowserver.idl"

Processing C:Documents and SettingsColin J TalbotDesktopSiliconCowserver.idl
server.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeoaidl.idl
oaidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeobjidl.idl
objidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeunknwn.idl
unknwn.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludewtypes.idl
wtypes.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeasetsd.h
basetsd.h
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeguiddef.h
guiddef.h
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeocidl.idl
ocidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeoleidl.idl
oleidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeservprov.idl
servprov.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeurlmon.idl
urlmon.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludemsxml.idl
msxml.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeoaidl.acf
oaidl.acf
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeocidl.acf
ocidl.acf
midl : error MIDL2212 : error while writing to file .server_p.c

SiliconCow build failed.

Regards.
Colin.

[CJTalbot]

I just had a look at .server_p.c and saw it was read only, removed this attrib and now shows another error :s :

------ Build started: Project: SiliconCow, Configuration: Debug|Win32 ------


Deleting intermediate files and output files for project 'SiliconCow', configuration 'Debug|Win32'.

Generate Fortran include file

deftofd "C:Documents and SettingsColin J TalbotDesktopSiliconCow esource.h" "C:Documents and SettingsColin J TalbotDesktopSiliconCow esource.fd"

Creating Type Library...

MIDL /D "_DEBUG" /nologo /env win32 /tlb "Debug/SiliconCow.tlb" "C:Documents and SettingsColin J TalbotDesktopSiliconCowserver.idl"

Processing C:Documents and SettingsColin J TalbotDesktopSiliconCowserver.idl
server.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeoaidl.idl
oaidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeobjidl.idl
objidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeunknwn.idl
unknwn.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludewtypes.idl
wtypes.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeasetsd.h
basetsd.h
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeguiddef.h
guiddef.h
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeocidl.idl
ocidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeoleidl.idl
oleidl.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeservprov.idl
servprov.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeurlmon.idl
urlmon.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludemsxml.idl
msxml.idl
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeoaidl.acf
oaidl.acf
Processing c:Program FilesMicrosoft Visual Studio 8VCPlatformSDKincludeocidl.acf
ocidl.acf


Compiling resources...

Rc /d "_DEBUG" /l 0x0809 /I "Debug" /I "Debug" /fo "Debug/SiliconCow.res" "C:Documents and SettingsColin J TalbotDesktopSiliconCowSiliconCow.rc"

fatal error RC1109: error creating Debug/SiliconCow.res

SiliconCow build failed.

[Steven_L_Intel1]

Looks as if you have more read-only files. Try deleting everything in the Debug and Release folders and rebuild.

[CJTalbot]

Indeed more read only files, not sure if this is ever going to work as I now have 32 errors on the screen and it is only 32 as it has stopped trying to build because of so many errors and to add salt to the wounds this is only showing errors for 1 .f90 file and I have about 30.

As I didn't create the program in the first place I think it is going to be very hard to upgrade it, do you know of any easy way to do this?

The error that seems to be showing its ugly head the most is the following:

Error 7 Error: A dummy argument of a statement function must be a scalar identifier. [3] C:Documents and SettingsColin J TalbotDesktopSiliconCowLargeIntestine.f90 359

I would like to thank you for your help so far and I would appreciate any further advice you could give.

Regards,
Colin.

[Steven_L_Intel1]

At this point I'd need to see the source file. You can submit it to Intel Premier Support (please ask that the issue be assigned to Steve Lionel) or attach it to a reply here (click on Options while replying).

[CJTalbot]

Hello,

Please find attached the Source Code.

Regards,
Colin.

[Steven_L_Intel1]

Wow - a COM Server application.

There was at least one real syntax error in there, plus another error which I don't think CVF would have accepted. Anyway, here's the changes I made which allowed it to build:

In LargeIntestine.f90, line 3, add a comma after "USE Rumen"
In odeint.f90, line 41, change 'iosdef.for' to 'for_iosdef.for'
In UISiliconCow.f90, line 109, change DFPORT to IFCORE (this ought not to be necessary - I have to figure out why)
In ISiliconCow.f90, line 139, change '_SysStringLen@' to '_SysStringLen@4'

You'll get a couple of compile-time warnings which you can ignore and some link warnings that I think you can ignore.

[CJTalbot]

Excellent,

I will give it a go and let you know how I get on.

Many Thanks,

Colin.

[CJTalbot]

Right, I have made the changes you specified but Im still getting lots of errors on the screen. Is it possible if you could upload the changes and I will see if still Im getting the same problem?

Regards,
Colin.

[Steven_L_Intel1]

This is not the proper place for that sort of exchange. Please open an issue with Intel Premier Support and ask that it be assigned to Steve Lionel. We'll take it from there.

[CJTalbot]

This has been done.

Issue Number: 415131

[jdchambless]

Hi Steve,
I am getting an error much like this one, concerning _SysStringLen@. Each time I change one of the arguments in the COM server hierarchy, or just one of the properties of one of the arguments (say from Real(8) to Real(4)), the compilation fails and I have to go back and put a "4" at the end of _SysStringLen@ in my Iclassname.f90 file. Any ideas why this keeps resetting itself to _SysStringLen@ without the "4" on the end?
Thanks,
Jason C.

[Steven_L_Intel1]

What's generating the .f90 - CVF or IVF? If it's IVF, that's a bug.

[jdchambless]

I created this In-Process COM Server with the latest version (10.0.025) of the IA32-only Intel Visual Fortran compiler. It is an evaluation version, but I'm not sure that should matter much.
Thanks,
Jason C.

[Steven_L_Intel1]

Ah, I see. That's a bug - I'll report it.