Wine Installation

[calemarie]

Hi!

I have a silly question for anyone who can help. I want to install intel fortran for Windows under Wine. I know there is a Linux flavour of the compiler, but the purpose is to produce win32 executables on a linux-powered server. The server is only used for file storage and hopefully compilation. Execution would be deferred on another, windows-powered machine. I thought this would do the trick.

I managed to get up to the setup screen, but I now face three problems:

• the setup window is too small, and not resizable -> I can not read the buttons and hence, click the right one;
• a few "blind guess" and tab key hits later, I managed to get to the license screen, where everything fails with an error message: I suspect the check for platform / intel fortran version to hang because of the use of linux.
• using the text-user interface, the installation crashes with the following error message:

[lca@redhat ~]$ wine /media/w_cprof_p_11/Setup.exe /s /eula=accept
fixme:winhttp:WinHttpCheckPlatform stub
err:msi:MsiEnableLogW Unable to enable log L"C:\\windows\\temp\\FortranProfessional.Log"
fixme:shell:IsUserAdmin stub
fixme:console:AttachConsole stub ffffffff
[lca@redhat ~]$

Googling didn't help much on this...

My questions are the following:

• is there a way to get intel fortran for windows to work under wine?
• is there another way to handle my situation (windows executable compilation under linux) knowing that we ought to use intel fortran as a compiler given our "quality procedure"?

Thank you in advance for any hint,
calemarie

[TimP]

Are you hoping to run PPE under Wine?
How does using a compiler in an unsupported way satisfy your quality procedures?

[calemarie]

Quoting - tim18

Are you hoping to run PPE under Wine?
How does using a compiler in an unsupported way satisfy your quality procedures?

Thank you for answering - and so quickly in addition!

Sorry if I look dumb, but what do you call PPE exactly?

The objective here is to store the source code on the linux server, using a bunch of existing scripts and procedures. Then, the idea would be to compile a win32 executable and re-distribute it or optionnaly execute it locally via wine (this last point still to be discussed).

Regarding quality procedures, the QA department validated this particular compiler during a 6 months study years ago, checking old and new executables, comparing results, stating if round-ups would be acceptable... Obviously, they are not keen to change easily their conclusions. I know this is a non-sense, but I do not have the power to change this, unfortunately.

calemarie

[Steven_L_Intel1]

PPE = Visual Studio 2005 Premier Partner Edition, the IDE. I don't think you've gotten that far. I don't know what Wine is returning that the install doesn't like.

Sorry, but what you're doing is completely unsupported. We do not test installing or using the Windows compiler under Windows emulators on non-Windows systems. If it happens to work, fine, but if it doesn't, we can't help.

[calemarie]

Quoting - Steve Lionel (Intel)

PPE = Visual Studio 2005 Premier Partner Edition, the IDE. I don't think you've gotten that far. I don't know what Wine is returning that the install doesn't like.

Sorry, but what you're doing is completely unsupported. We do not test installing or using the Windows compiler under Windows emulators on non-Windows systems. If it happens to work, fine, but if it doesn't, we can't help.

Indeed, I'm not into IDE yet, only console compilation would be fine.

I will try to digg a bit more, and if I happen to find any positive setup, I will post here. Otherwise, I will have to find an alternate!

Thank you for your time and explainations.

calemarie

[bendel_boy1]

Quoting - calemarie

Indeed, I'm not into IDE yet, only console compilation would be fine.

I will try to digg a bit more, and if I happen to find any positive setup, I will post here. Otherwise, I will have to find an alternate!

Thank you for your time and explainations.

calemarie

I appreciate that this isn't the answer you want, but would you not be better off looking to use gfortran? This should be easier to run under Wine, and from the gcc documentation it seems that you could use a native Linux compiler with a flag to produce a Win32 executable.

[calemarie]

Quoting - bendel boy

I appreciate that this isn't the answer you want, but would you not be better off looking to use gfortran? This should be easier to run under Wine, and from the gcc documentation it seems that you could use a native Linux compiler with a flag to produce a Win32 executable.

Hi,

Indeed, I'm stuck with Intel Fortran because of the use of antic keywords back to MS-DEV, and possibly older. In addition to this, I need to include suppliers windows DLLs, which I have been unable to do with gfortran (I could include self-made DLLs, but not the external ones).

As a matter of fact, I finally achieved to install ifort for windows within wine. I am left with the license issue right now, and some lib path definitions to be updated. I can definitely compile a single source code with no particular trouble.

Next step is to go through the whole nine yards: the full project. I will keep you informed as soon as I end up with something.

Regards,
calemarie

[TimP]

Quoting - calemarie

I'm stuck with Intel Fortran because of the use of antic keywords back to MS-DEV, and possibly older.

Requiring the use of MS Powerstation syntax in combination with older non-standard extensions is more like an anti-quality procedure.

[calemarie]

Quoting - tim18

Requiring the use of MS Powerstation syntax in combination with older non-standard extensions is more like an anti-quality procedure.

I second that, but am unfortunately not in a position to change the local IT policy on this subject. We are dealing with hundreds of in-house softwares developped along the last decades for both Unix and Windows. We are now moving onto a new server with a single source code repository - under Linux - and everybody is crossing their finger, hoping that this move will not induce too much code re-writing. Hence the trick of intel fortran for windows under wine.

Still struggling with the license for now...

calemarie

[Steven_L_Intel1]

What are the details of the license problem?

[calemarie]

Quoting - Steve Lionel (Intel)

What are the details of the license problem?

Actually, I just found out the issue: the license file was not correctly located. Intel fortran looks after lic files in a "trusted source" or Z:/usr/bin location, while it was located under .wine/drive_c/Program Files... which is obviously not in the trusted source pool. I think the wine installation did perturb the normal setup. I copied the .lic files found into /usr/bin and could get a step further.

Still, this is with an evaluation license. I couldn't register with the serial number given. It seems that somehow, the server to which the install procedure connects finds out that I am running Linux, and does not accept a Windows serial number. Remote activation didn't help either (acceptatio code refused) and it seems to me that licensing servers require a license file, not a serial number. I may be wrong on this last point as I am not really into licensing servers...

Anyway, I now face a much more annoying "unrecognized source type" error. I have to digg a bit on that.

Regards,
calemarie

[Steven_L_Intel1]

Just register the serial number at the Intel Registration Center and it will email you a license file.

[calemarie]

Quoting - Steve Lionel (Intel)

Just register the serial number at the Intel Registration Center and it will email you a license file.

Thank you for the advice. I am currently working with a license file created during install. Even though I had a message in error at that time, it seems to me that this license is the good one, not the one for evaluation. How can I check this? It is written "permanent uncounted" in the one I use... Doesn't look like evaluation, does it?

Anyway, I now have a fully functionnal intel fortran compiler for windows compiling under wine! I had to struggle a bit with the lib path, but everything is running smoothly now.

Next step: an IDE...

Have a nice week end,
calemarie

[Steven_L_Intel1]

I agree that if it says "permanent" then that is not an evaluation license. Would you please email the license file to me at steve.lionel at intel.com? I'd like to see it. Thanks.

[calemarie]

Quoting - Steve Lionel (Intel)

I agree that if it says "permanent" then that is not an evaluation license. Would you please email the license file to me at steve.lionel at intel.com? I'd like to see it. Thanks.

Done: I sent you a PM enclosing the license file. We'll see after the 30 days evaluation period is over if this assumption proves correct.

I'm a bit surprised that the installation crashed with the serial number and went OK with the evaluation period, while on the contrary, the compiler fails with the evaluation license, and succeeds with the serial number. Anyhow, it's working.

Regards,
calemarie

[Steven_L_Intel1]

Thanks. Unfortunately, file attachments don't seem to work in PMs. (I see that there is an attachment, but can't open it.) Please email the file to me.

[Steven_L_Intel1]

I took a look at the license you're using. This is a commercial license, not evaluation, so that's why it says "permanent".

[calemarie]

Quoting - Steve Lionel (Intel)

I took a look at the license you're using. This is a commercial license, not evaluation, so that's why it says "permanent".

So I can mark this thread as "solved". Thank you all!

calemarie

[casir]

Quoting - calemarie

As a matter of fact, I finally achieved to install ifort for windows within wine. I am left with the license issue right now, and some lib path definitions to be updated. I can definitely compile a single source code with no particular trouble.

Hello,

We are trying to acheive the same here. We want to install Intel Visual Fortran under crossover (wine). Do you still have the details as to how you proceeded with your installation ?

I thank you in advance,

Benot Morin

[calemarie]

Quoting - casir

Hello,

We are trying to acheive the same here. We want to install Intel Visual Fortran under crossover (wine). Do you still have the details as to how you proceeded with your installation ?

I thank you in advance,

Benot Morin

Hi Benot,

Unfortunately, I did not manage to locate my notes on the installation right now. I will look after it and post back more details about the installation.

All in all, I remember that the installation went quit straightforward at the notable exception of the license issue.

Best regards,
calemarie

[calemarie]

Quoting - casir

Hello,

We are trying to acheive the same here. We want to install Intel Visual Fortran under crossover (wine). Do you still have the details as to how you proceeded with your installation ?

I thank you in advance,

Benot Morin

Hello Benot,

Finally found my install log file. Here are the steps involved for a RedHat EL5 (kernel 2.6.18):

1. update system
2. install wine
3. install Intel Fortran Compiler for Windows (under wine)

• go here http://www.microsoft.com/downloads/details.aspx?familyid=4A3AD088-A893-4F0B-A932-5E024E74519F&displaylang=en and get the file msxml3.msi
• move .wine/drive_c/windows/system32/msxml3.dll to .bak
• run winecfg and set msxml3 to native
• run $ wine msiexec /i msxml3.msi
• emulate a 1600x1200 virtual desktop if your actual resolution is lower (in order to reach buttons during setup!)
• run wine Setup.exe to install ifort
• select proper installation mode (serial number): installation will report in error due to incompatible platform (compiler for windows on a Linux machine)
• select evaluation installation

1. properly register the license file

• look for a .lic file on the hard drive (locate *.lic). You should find a license file in .wine/drive_c/Program Files/Common Files/Intel/Licenses/ with a part of the serial number in the name
• copy the license file in /usr/bin

There are some subsequent steps involving PATH modifications, but it seems that I didn't write this down... Sorry for that.

Best regards, and do not hesitate to ask again if something goes wrong during the procedure
calemarie