Problems between Intel Compiler 8.1 and Msc Marc 2007r1

kepzky606 · ‎11-03-2008

Hello,

I am using Intel Fotran Compiler in combination with MS VS 2003. I'd like to use the Intel Compiler with Msc Marc for executing my subroutines. But it does not work.

In the Visual environment I am able to create programs and the compiler works.

If I call a User subroutine out of Marc I get the following errormessages:

LINK : fatal error LNK1181: cannot open input file 'libmmt.lib'

Did anyone know what i have to do?

Kind regards

Erik

Steven_L_Intel1 · ‎11-03-2008

If you are linking from a non-Fortran project, make sure that the path to the Intel Fortran "lib" folder is present in the list of folders used for Library files. If this is a C++ project., use Tools > Options > Directories > Library Files to add this.

kepzky606 · ‎11-05-2008

Hello Steve,

I think that is not the problem.

I wrote an subroutine fr the FEM tool Marc. The routine is written in fortran 77 code.

In Mars I tried to compile this routine an then I get the errors.

To my opinion Marc is not able to call the compiler.

Is there an option to check if the compiler works correct?

What do I have to add to my environment variables?

Kind regards

Erik

at the moment I got this errormessage:

LINK : warning LNK4089: all references to 'mpich2mpi.dll' discarded by /OPT:REF

What can I do

Quoting - Steve Lionel (Intel)

If you are linking from a non-Fortran project, make sure that the path to the Intel Fortran "lib" folder is present in the list of folders used for Library files. If this is a C++ project., use Tools > Options > Directories > Library Files to add this.

Steven_L_Intel1 · ‎11-05-2008

I am not familiar with Marc so I can't comment in detail. I will note that the "error message" is not an error - it's simply saying that the linker was asked to link to a DLL but there were no calls to that DLL from the program. You can ignore it. Are you seeing any other errors?

8.1 is old enough that I don't remember all the details, but you would set up the command line environment by using Start > Programs > Intel Software Development Tools > Intel Fortran Compiler 8.1 > Build Environment for 32-bit applications.

Whatever is invoking the compiler would want to use the "ifort" command. If you need more help, show us the commands actually being used and any error messages.

TimP · ‎11-05-2008

If your build expects mpich2 to be installed prior to compiling, you must do that. Intel MPI is 99% compatible, and may do the job as well. Surely that is described in the requirements, along with the specification of compiler.

kepzky606 · ‎11-06-2008

Quoting - tim18

If your build expects mpich2 to be installed prior to compiling, you must do that. Intel MPI is 99% compatible, and may do the job as well. Surely that is described in the requirements, along with the specification of compiler.

@Tim, Lionel

Thank you very much for your help. Now everything works fine.

Kind regards

Erik

freesun · ‎11-25-2008

Quoting - kepzky606

Quoting - tim18

If your build expects mpich2 to be installed prior to compiling, you must do that. Intel MPI is 99% compatible, and may do the job as well. Surely that is described in the requirements, along with the specification of compiler.

@Tim, Lionel

Thank you very much for your help. Now everything works fine.

Kind regards

Erik

Hi All..

and especially you kepzky606..I am also trying to build my subroutine in intel fortran environment for my analysis in Msc Marc and since i am new in both development environment my question goes all.

Firstly how do we generate files in intel fortran environment those have .f or .for extensions since Marc needs only mentioned extensions? I am currently using 90 days evaluation version of intel fortran compiler 11.0.061 .When i select file/new project and i have choices like

Console App.

Library

Quick Win Application

Windowing App.

Com Server etc.

Which one is suitable for me?.I indeed tried all and they all give me .f90 file extension.And even i tried "save as" but couldnt find .f or .for extensions.

thanks in advance..

Well kepz..after creating

my question goes all in fact i am new to

TimP · ‎11-25-2008

Quoting - freesun

I am also trying to build my subroutine in intel fortran environment for my analysis in Msc Marc

Which one is suitable for me?.I indeed tried all and they all give me .f90 file extension.And even i tried "save as" but couldnt find .f or .for extensions.

The only differences associated with the file name choices are that .f and .for default to the fixed column field source code format of Fortran 77, while .f90 defaults to the free format of Fortran 90. Either should work for your purpose. As for relinking Marc, you will have to rely on their instructions. If you are using a discontinued version, the help you get may be limited.

Steven_L_Intel1 · ‎11-25-2008

Quoting - freesun

Firstly how do we generate files in intel fortran environment those have .f or .for extensions since Marc needs only mentioned extensions? I am currently using 90 days evaluation version of intel fortran compiler 11.0.061 .When i select file/new project and i have choices like

Console App.

Library

Quick Win Application

Windowing App.

Com Server etc.

Which one is suitable for me?.I indeed tried all and they all give me .f90 file extension.And even i tried "save as" but couldnt find .f or .for extensions.

What you are looking at is project creation, not source file creation. Unless you know differently, choose Console Application as the project type. You can then opt to have either an empty project with no source files or one with sample file(s) which you can edit or remove as desired.

To add a new source file to a project, use the Project > Add to project > New File. You can then choose free-form or fixed form Fortran source and it will default to the correct file type.

freesun · ‎11-30-2008

Quoting - Steve Lionel (Intel)

What you are looking at is project creation, not source file creation. Unless you know differently, choose Console Application as the project type. You can then opt to have either an empty project with no source files or one with sample file(s) which you can edit or remove as desired.

To add a new source file to a project, use the Project > Add to project > New File. You can then choose free-form or fixed form Fortran source and it will default to the correct file type.

Hi Steve and tim thnks bot for replying me..

well Steve i tried wht you said and still didnt find solution to my question.So i am attaching a jpg file what i had done and got from steps i choosed.

freesun · ‎11-30-2008

Quoting - freesun

Quoting - Steve Lionel (Intel)

What you are looking at is project creation, not source file creation. Unless you know differently, choose Console Application as the project type. You can then opt to have either an empty project with no source files or one with sample file(s) which you can edit or remove as desired.

To add a new source file to a project, use the Project > Add to project > New File. You can then choose free-form or fixed form Fortran source and it will default to the correct file type.

Hi Steve and tim thnks bot for replying me..

well Steve i tried wht you said and still didnt find solution to my question.So i am attaching a jpg file what i had done and got from steps i choosed.

http://img140.imageshack.us/my.php?image=stepsgh1.jpg][IMG]http://img140.imageshack.us/img140/1503/stepsgh1.th.jpg

Steven_L_Intel1 · ‎11-30-2008

Regarding the file type - just erase the "90" from .f90 and it will work fine.

The error message suggests that the 32-bit compiler is not installed. In Visual Studio, select Tools > Options > Intel Visual Fortran > Compilers. With the Target Platform selected as Win32, what does it show for Selected Compiler and Executables?

freesun · ‎12-01-2008

Quoting - Steve Lionel (Intel)

Regarding the file type - just erase the "90" from .f90 and it will work fine.

The error message suggests that the 32-bit compiler is not installed. In Visual Studio, select Tools > Options > Intel Visual Fortran > Compilers. With the Target Platform selected as Win32, what does it show for Selected Compiler and Executables?

Hi Steve;

I followed what you said and in the mentioned address i couldnt find the "compiler" option to change :(

Is it due to having 90 days evaluation version? Some settings might not be installed ...

I am again sending the snapshot of my screen

http://img504.imageshack.us/my.php?image=errorrn1.jpg

I am using windows vista Turion 64 x2 ( so i installed evaluation version of w_cprof_p_11.0.061_intel64.exe after installing vs2008 and then tried to compile a sample code. Do i have to change some settings before compiling? other than you mentioned above? )

thanks for your interest

freesun · ‎12-01-2008

Quoting - freesun

Quoting - Steve Lionel (Intel)

Regarding the file type - just erase the "90" from .f90 and it will work fine.

The error message suggests that the 32-bit compiler is not installed. In Visual Studio, select Tools > Options > Intel Visual Fortran > Compilers. With the Target Platform selected as Win32, what does it show for Selected Compiler and Executables?

Hi Steve;

I followed what you said and in the mentioned address i couldnt find the "compiler" option to change :(

Is it due to having 90 days evaluation version? Some settings might not be installed ...

I am again sending the snapshot of my screen

http://img504.imageshack.us/my.php?image=errorrn1.jpg

I am using windows vista Turion 64 x2 ( so i installed evaluation version of w_cprof_p_11.0.061_intel64.exe after installing vs2008 and then tried to compile a sample code. Do i have to change some settings before compiling? other than you mentioned above? )

thanks for your interest

Sorry i should have double cliked "Intel Visual Fortran" text , so below there is snapshot shows what i have

http://img440.imageshack.us/my.php?image=compileroptionkb9.jpg

it says no compiler installed ..and now where can i install it ? as i mentioned above i had already installed intel64.exe compiler :(

Steven_L_Intel1 · ‎12-01-2008

You installed the compiler for Intel 64, but the default configuration in Visual Studio is for IA-32 (Win32). If you want to build for Intel 64, do this.

Build > Configuration Manager
Under Active Solution Platforms, select
In the dialog that comes up, select x64 as the new platform (probably already set by default), and click OK
Click Close.

Now your configuration is set to build for Intel 64.

If you want to build for IA-32, then download and install the "_ia32.exe" package.

freesun · ‎12-05-2008

Quoting - Steve Lionel (Intel)

You installed the compiler for Intel 64, but the default configuration in Visual Studio is for IA-32 (Win32). If you want to build for Intel 64, do this.

Build > Configuration Manager

Under Active Solution Platforms, select

In the dialog that comes up, select x64 as the new platform (probably already set by default), and click OK

Click Close.

Now your configuration is set to build for Intel 64.

If you want to build for IA-32, then download and install the "_ia32.exe" package.

Hi Steve;

Thank you for your guidance..

I followed above steps and changed the configuration but now it gives same error saying that this time win64 compiler is not installed :(

i think i d bettter install another exe package for my wista platform.

Steven_L_Intel1 · ‎12-05-2008

I suggest you download and install the package with a name ending in _novsppe.exe and try again.

dadaya · ‎04-15-2009

Quoting - kepzky606

Quoting - tim18

If your build expects mpich2 to be installed prior to compiling, you must do that. Intel MPI is 99% compatible, and may do the job as well. Surely that is described in the requirements, along with the specification of compiler.

@Tim, Lionel

Thank you very much for your help. Now everything works fine.

Kind regards

Erik

dadaya · ‎04-15-2009

Quoting - dadaya

Quoting - kepzky606

Quoting - tim18

If your build expects mpich2 to be installed prior to compiling, you must do that. Intel MPI is 99% compatible, and may do the job as well. Surely that is described in the requirements, along with the specification of compiler.

@Tim, Lionel

Thank you very much for your help. Now everything works fine.

Kind regards

Erik

dear kepzky606,I have the same problem like you when i learn marc,the problem as followed:
LINK : warning LNK4089: all references to 'mpich2mpi.dll' discarded by /OPT:REF
would you please do me a favor to tell me how to solve the problem in detail.i will appreciate for your help.Look forward to your reply

Reza_M_ · ‎11-06-2014

Hello

I am also trying to link my subroutine to MSC.Marc 2013.

I am using intel(R) visual fortran compiler installed together with Microsoft visual studio in order to run MSC.Marc with subroutines.

I wrote the following subroutine to extract nodal stress values. It perfectly writes down the nodal stresses in MSC.Marc 2005r3 installed for Linux; however, when I try to implement this subroutine in MSC.Marc 2013 installed for Windows using intel(R) visual fortran compiler, error "forrt1: severe <157>: Program Exception - access violation" occurs.

The subroutine is:

subroutine impd(lnode,dd,td,xord,stnod,f,v,a)

include '../common/implicit'

include '../common/array3'

include '../common/array2'

include '../common/spacevec'

include '../common/strvar'

include '../common/concom'

include '../common/elmcom'

include '../common/dimen'

integer j

character NodeStress*90

dimension lnode(2)

dimension dd(ndeg),td(ndeg),xord(ncrd),f(ndeg),

*v(ndeg),a(ndeg)

310 format(I4,(1H:),6E14.6)

if(lnode(2).ne.1) return

if(lnode(1).eq.1) then

write(NodeStress,'(a,i4.4,a,$)') './NodalStress_',inc,'.dat'

open(unit = inc+1000 ,file=NodeStress,status="new")

c if(lnode(1).eq.1) then

write(inc+1000,'(17Hlabel=NodalStress)')

write(inc+1000,'(13Hnum_item=3800,/)')

end if

open(inc+1000)

write(inc+1000,310) lnode(1)-1,(stnod_d((lnode(1)-1)*6+j),

+j=1,6)

return

end

I would appreciate if you could help me to figure out the problem.

Kind Regards,

Reza

Steven_L_Intel1 · ‎11-06-2014

It's not possible to determine the problem from the information provided. You need to run the application under the debugger and see where it is when the error occurs, then determine which variable or operation is triggering the problem. It has nothing to do with linking. Do also make sure that you are not mixing STDCALL and C calling mechanisms (32-bit only).