Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

compile siesta-4.0 code by intel fortran

soumaia_d_
Beginner
‎02-19-2017 01:02 PM
778 Views

Hi all

I want compile siesta-4.0 code by intel fortran parallel_studio_xe_2017update1 but i don't know how to do it, when i apply the installation steps of this code in my cluster ( linux fedora24 system ) the gnu fortran who is doing the compilation what can i do to solve this problem ? 

with best regard Soumaia

 

0 Kudos

Link Copied

1 Reply
mecej4
Honored Contributor III
‎02-20-2017 07:56 AM
778 Views

I do not know what Siesta-4 is or where to find it, but the following is typical for all Fortran builds on Unix/Linux:

There is usually a makefile or a makefile.inc file in which the compiler, compiler options and other configuration information can be customized. Typically, the makefile will contain a line that defines the symbol FC (which stands for Fortran Compiler). It is probably set to "gfortran", and should be set to "ifort" instead. Similarly, compiler options have different abbreviations in different compilers, so you may need to change those as well. Finally, you should do the build in a shell window that has the Intel script ifortvars.sh sourced.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.