ifortvars under cygwin

[janilo]

Dear all,

Weare currently facing some problemswith our Intel Fortran Compiler V9.1installation on our Windows 2000 cygwin server and I'm hoping that you can help me further with it.

Just to let you know up front: Our external users can access this server only via UNIX, therefore it is not possible to launch the ifort environment firstin a cmd window and then to start cygwin. We are obliged to start cygwin first (even if everything works fine with the ifort-first solution!).

That's why we havere-written the ifortvars.bat file into a ifortvars.ksh version (see below), which we,up to now,tried to launch eitherfrom the .kshrc_cygwin fileor directly in the terminal session. Both times with the same limited success ...

Limited success means in this case that we are able to compile some files, whereas some other compilations abort with thefollowing error message:

ifort -unix -compile_only opersy.for -object:OBJ/opersy.o
Intel Fortran Compiler for 32-bit applications, Version 9.1 Build 20070322Z
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
fortcom: Fatal: There has been an internal compiler error (C0000005).
compilation aborted for opersy.for (code 1)
make: *** [OBJ/opersy.o] Error 1

So to summarize: No error messages with Intel Fortran V9.1 under UNIX, no error messages withIntel Fortran V9.1 under Windows cmd.exeand theifort-first-then-cygwin solution, but above mentioned errors while running the compilation under cygwin with translated ifortvars.ksh script.

Any ideas what we could have missed? Is there maybe still an error in the script below, which I just don't see?

Thanks a lot for your help.

Kind regards
Janine

______________________________________________________________________

echo "/cygdrive/c/program files/Microsoft Visual Studio 8/VC/bin/vcvars32.bat"

export VSINSTALLDIR="/cygdrive/c/progra~1/micros~4"
export VCINSTALLDIR="/cygdrive/c/progra~1/micros~4/VC"
export FrameworkDir="/cygdrive/c/WINNT\\Microsoft.NET/Framework"
export FrameworkVersion="v2.0.50727"
export FrameworkSDKDir="/cygdrive/c/progra~1/micros~4/SDK/v2.0"

export LIB="C:\\Program Files\\Microsoft Visual Studio 8\\VC\\ATLMFC\\LIB;C:\\Program Files\\Microsoft Visual Studio 8\\VC\\LIB;C:\\Program Files\\Microsoft Visual Studio 8\\VC\\PlatformSDK\\lib;C:\\Program Files\\Microsoft Visual Studio 8\\SDK\\v2.0\\lib;%LIB%"

export IFORT_COMPILER91="/cygdrive/c/progra~1/intel/compiler/fortran/9.1"
export INTEL_SHARED="/cygdrive/c/progra~1/common~1/intel/shared~1"
export INTEL_LICENSE_FILE="xxx"

echo "Setting environment for using Microsoft Visual Studio 2005 x86 tools."

export DevEnvDir="/cygdrive/c/progra~1/micros~4/Common7/IDE"

export PATH="/cygdrive/c/progra~1/micros~4/Common7/IDE:/cygdrive/c/progra~1/micros~4/VC/BIN:/cygdrive/c/progra~1/micros~4/Common7/Tools:/cygdrive/c/progra~1/micros~4/Common7/Tools/bin:/cygdrive/c/progra~1/micros~4/VC/PlatformSDK/bin:/cygdrive/c/progra~1/micros~4/SDK/v2.0/bin:/cygdrive/c/WINNT/Microsoft.NET/Framework/v2.0.50727:/cygdrive/c/progra~1/micros~4/VC/VCPackages:$IFORT_COMPILER91/ia32/bin:$INTEL_SHARED/ia32/bin:$PATH"
export INCLUDE="/cygdrive/c/progra~1/micros~4/VC/ATLMFC/INCLUDE:/cygdrive/c/progra~1/micros~4/VC/INCLUDE:/cygdrive/c/progra~1/micros~4/VC/PlatformSDK/include:/cygdrive/c/progra~1/micros~4/SDK/v2.0/include:$IFORT_COMPILER91/ia32/include:$INCLUDE"
#export LIB="/cygdrive/c/progra~1/micros~4/VC/ATLMFC/LIB:/cygdrive/c/progra~1/micros~4/VC/LIB:/cygdrive/c/progra~1/micros~4/VC/PlatformSDK/lib:/cygdrive/c/progra~1/micros~4/SDK/v2.0/lib:$IFORT_COMPILER91/ia32/lib:$LIB"
export LIB="C:\\Program Files\\Intel\\Compiler\\Fortran\\9.1\\ia32\\lib;$LIB"
export LIBPATH="/cygdrive/c/WINNT/Microsoft.NET/Framework/v2.0.50727:/cygdrive/c/progra~1/micros~4/VC/ATLMFC/LIB"

echo fin

[TimP]

Did you try something along the line of
cygstart cmd.exe "/E:ON /V:ON /K "C:\Program Files\Intel\...\bin\ifortvars.bat" "
(try to use the exact ifortvars command which the compiler installed on the Start menu)
in order to replicate the working scheme of running ifortvars under cmd.exe?
I think it's going to be difficult to get help on this, as we haven't been permitted to run Windows 2000 for years, and even the good versions of ifort 9.1 probably didn't get a lot of testing under that OS.
Cygwin makes a valiant effort to keep unsupported versions of Windows alive, but there are limits.

[janilo]

Hi Tim,

thanks for the quick reply.

We tried to place the ifortvars.bat call (exactly as it can be seen in the properties of the "Build environment ..." Start menu entry)directly in the cygwin.bat file, but it didn't work well.
The settings did not go through and we had to launch our own ifortvars.ksh script again under cygwin to get at least some of the necessary environment settings. Of course with the same bad results.

Is there any other/better possibility to place this call?

Thanks again.
Janine

[janilo]

Hello,

Unfortunately I have to come up with this topic again ...

We have now migrated our old Windows 2000 server to Windows XP (no changeof compiler version, still 9.1) and I was hoping that this might solve the internal compiler error we encountered a few months ago, but unfortunately it didn't.

I can exactly reproduce the behavior described above, but now under WinXP:

- compilation directly under UNIX - OK
- compilation under cygwin, when launching the ifort environment first -OK
- compilation under cygwin, when starting the cygwin shell first and then sourcing the ifortvars.ksh script - KO (compilation aborted for at least one of the .for files with "internal compiler error (C0000005)")

Maybe you are now able to analyse this problem more closely? If so, just let me know and I will send you some example files (if possible in a separate mail ...).

Thanks in advance for your help.

Kind regards
Janine

[Steven_L_Intel1]

Compiler version 9.1 is no longer supported. If you want, you can attach a ZIP of the sources here along with instructions on how to reproduce the problem (including command line used.) I will see if I can reproduce the error with the current compiler version and let you know. If you want, you can mark your post with the attachment as "Private" so that other users will not be able to see it.

[Steven_L_Intel1]

No errors when building with the current version (Intel Visual Fortran Composer XE 2011 Update 6) on Windows 7.

[janilo]

Did you test this under Cygwin? Without starting the ifort environment first?

Thanks
Janine

[TimP]

No, I always do it the easy way:
Open ifort command prompt window
run cygwin.bat in that window.
You could make a shortcut which takes both steps automatically in the normal order.

[janilo]

Ok, with this config the compilation runs also under XP and with V9.1.

But since our subcontractors can only connect to the Cygwin server via telnet, they don't have the possibility to launch the ifort env first. Therefore I have to get it running also the other way round ...

Is there maybe something wrong with the code of the opersy file which couldcause the internal compiler error? Independent from the environment?

Thanks again
Janine

[Steven_L_Intel1]

Impossible to say without detailed investigation, and as 9.1 is very old we won't do that.