fortcom.exe hangs?

[abhimodak]

I am seeing a weird "hang-up" of fortcom.exe when trying to build a dll and exe of a mixed langauge project. This happens only with the x64 version of the build using 11.1.051. I am using WinXP64 with VS2005.

We have built (and continue to do so) this project in IVF compiler versions starting from v9.* on a nightly basis. We don't see this problem when building 32-bit binary with 11.1.0.51.

More specifically, there are following steps in the build: (a) build a library using all Fortran files. (b) create a dll and ext. When creating the dll thin wrapper of C++ is used. We specify the system libraries and use /iface:cvf, /names:lowercase, and /assume:underscore when building the Fortran library.

All the compilation and creation of a static library from the Fortran programs goes fine. While building the dll, fortcom.exe just hangs up. I would once again stress that we can use exact same set of files with all versions of compiler starting from version 9.0 to 11.1.046 for both Win32 and x64 binaries. This problem happens only with 11.1.051 when building x64 binary.

Any suggestions?

Abhi

[TimP]

Quoting - abhimodak

Any suggestions?

check your disk

[abhimodak]

Hi Tim

Check the disk for? I have at least 5 GB of free space on the harddrive...

As mentioned in the first post, I can build x64 binaries when using 11.1.046; on the same disk just by changing the what command prompt I launch from All Program --> Intel Software Development Tools. Note also that I can build win32 binaries with 11.1.051.

Abhi

[TimP]

hard disk drives>properties>check

[Steven_L_Intel1]

Are you willing to provide us with a ZIP of your solution folder (Clean it first) so that we can try it?

[abhimodak]

Hi Steve

That's going to be difficult. I vacillated for at least 10 days before posting this question since I knew I am not permitted to share the solution. I am trying to see if I can reproduce this behavior with a sample program.

I am doing a disk property check right now but I really wonder if that has anything to do with this. Sorry for this dumb remark Tim, but I have no clue why you are suggesting this. I am doing teh disk check since I trust you :)

Abhi

[abhimodak]

Hi

Just wanted to report here that this problem (of fortcom.exe hanging) has gone away with 11.1.054! As I had mentioned before, I have been buiding this project with virtually very compiler update since 10.0.025 for both win32 and win64 but never had this issue. To the best of my understanding, nothing in the build script has changed.

Steve's earlier suggestion indicates that there could have been some problem with the linker executable. Hopefully, the new update has it right.

Sincerely
Abhi

[Steven_L_Intel1]

Glad to hear it.

[Jugoslav_Dujic]

Now it's my turn :(. I see the same behavior on Windows 7, x64 with 11.1 update 6; mixed-language solution with ~40 projects. Several Fortran projects do build, but a couple just reach the "Linking..." stage and stay there for hours. Task manages shows as much as 6 fortcom.exe processes, each taking its share of CPU (and changing), but only one xilink.exe, sitting idle at 0 cpu and 960 kB memory.

I can send the solution (although you can imagine it's big), but not immediately.

...indeed, killing the xilink.exe makes the build continue (although, of course, unsuccessfully).

[Steven_L_Intel1]

Well, you know the drill, Jugoslav. Send us the solution when you have it. If it's large, it might be better to do it through Premier Support.

It's reasonable for xilink to be just sitting there - it spawns fortcom.exe. I find it somewhat puzzling that you have only one xilink process, though.

Can you build proijects individually? Is there one project which triggers the problem?

[Jugoslav_Dujic]

Have you perhaps missed my reply? (It's not urgent, just to make sure you noticed it.)

[Steven_L_Intel1]

I have it. StateModeF is missing. Do I need it?