- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would recommend to add something like
source /opt/intel/ ... /compilervars.sh
to your user account .bashrc to always have the environment set up correctly for the compiler
Thanks, Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
# source /opt/intel/composer_xe_2011_sp1.11.339/bin/compilervars.sh
# source /opt/intel/composer_xe_2011_sp1.11.339/bin/compilervars.csh
but, yet that error occur !
root@abbaszade-virtual-machine:~/MFIX/tutorials/FluidBed_DES# sh ../../model/make_mfix
*******************************************
* Creating the MFIX-executable mfix.exe *
* Version 2010-1 *
*******************************************
MFIX directory is /home/abbaszade2/MFIX/model
Do you need SMP version? (y/n) [no]
Do you need DMP version? (y/n) [no]
Do you need debug version? (y/n) [no]
Force re-compilation of source files in run directory? (y/n) [no]
64 bit Linux system detected, please select compiler.
==============================================================
MFIX Compilation directives available for following compilers:
==============================================================
[1] Intel Fortran Compiler (IFORT - FCE for 64 bit)
[2] Intel Fortran Compiler (IFORT - FCE for 64 bit) on AMD Opteron
[3] Portland Group Linux Fortran Compiler (pgf90)
[4] PathScale compiler (pathf90)
[5] Portland Group Linux Fortran Compiler (pgf90) on AMD Opteron
[6] Portland Group Linux Fortran Compiler (pgf90) on Cray XT3 at PSC
[7] Portland Group Linux Fortran Compiler (pgf90) on Cray XT4 at NCCS
[8] PathScale Compiler (pathf90) on Cray XT4 at NCCS
[9] Pathscale Compiler (pathf90) on Cray XT4 at NERSC
[10] IBM Fortran Compiler (xlf90) on Blue Gene at ANL ALCF
[11] gfortran
Select the compiler to compile MFIX? [1] 1
Intel Compiler selected
______ If you get 'ifort: Command not found' _______
IFORT environment variables are not defined
Please add the following in your shell and rerun make_mfix
for .cshrc 'source path_to_fce_9.0/bin/ifortvars.csh'
for .kshrc or .bashrc 'source path_to_fce_9.0/bin/ifortvars.sh'
Compiling with machine-dependent file LINUX_intel.F
Ignore messages such as "Cannot access *.f or *.inc"
ls: cannot access *.f: No such file or directory
ls: cannot access *.inc: No such file or directory
Files from run directory used for making Mfix:
ls: cannot access *.0*: No such file or directory
******************************************************
Preparing files for your serial/smp compilation
******************************************************
Compiling inline files . . .
*******
make -f mfix_l_not.make compare.o eosg.o discretize.o
ifort -c -I. -w -w95 -i_dynamic -convert big_endian -assume byterecl -FR -O3 -axW -ip -fp-model precise -ftz param_mod.f
make: ifort: Command not found
make: *** [param.mod] Error 127
Please wait . . .
make -f mfix_l_not.make mfix.exe
ifort -c -I. -w -w95 -i_dynamic -convert big_endian -assume byterecl -FR -O3 -axW -ip -fp-model precise -ftz param_mod.f
make: ifort: Command not found
make: *** [param.mod] Error 127
*** File mfix.exe NOT created.
I remind that my ubuntu is version12.04 and my IFORT version is 2011.11.339. when I install ifort, it messaged ifort not supported the this version of OS .
what can I do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IIRC the standard shell on Ubuntu is dash (sh is linked to it). I'd recommend to invoke the build via:
root@abbaszade-virtual-machine:~/MFIX/tutorials/FluidBed_DES# /bin/bash ../../model/make_mfix
Btw.: I see you kicked-off the build as user root (which is not good practice). Did you update the .bashrc initialization file for the same user?
Best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
this looks like a project being tailored for pre-12.x compilers.
First, with 12.x we changed "ifortvars.sh" (and "iccvars.sh") to "compilervars.sh" PLUS argument, which is either "intel64" (64 bit) or "ia32" (32 bit), e.g.:
$ source /opt/intel/composer_xe_2011_sp1.11.339/bin/compilervars.h intel64
You did not use any argument above. To me it looks like "ifort" was found, though. Maybe you did provide an argument in your case.
Second, we also changed the directory structure beginning with Intel MKL 10.3. Before, we had 64 bit libraries in "em64t" sub-directory. Now it's "intel64". Also see:
http://registrationcenter.intel.com/irc_nas/1977/mklnotes_10.3.0.htm
You only need to make sure that Intel MKL libraries are found in the correct directory:
...
-o mfix.exe odepack.a -L /opt/intel/composer_xe_2011_sp1.11.339/mkl/lib/intel64-lmkl_lapack -lmkl_em64t -lmkl_core -lvml -lguide -lpthread
Best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello there, also a newbie here.
So far, all pages I found about this subject recommend editing your .basrc file. I have tried many things, like adding all of these at the end of my .bashrc file, all failures:
Code:
source /opt/intel/composer_xe_2015.3.187/bin/intel64/ifortvars.sh intel64
source ~/opt/intel/composer_xe_2015.3.187/bin/ifortvars.sh intel64
source /root/opt/intel/composer_xe_2015.3.187/bin/intel64/ifortvars.sh intel64
The last one actually messed up my terminal, don't recommend it (when you start the terminal, you're not a superuser yet, so you don't have permission to access root, and it goes wrong, apparently).
The change that made a difference was actually this one:
Code:
PATH="/opt/intel/composer_xe_2015.3.187/bin/intel64:$PATH" export PATH LD_LIBRARY_PATH="/opt/intel/composer_xe_2015.3.187/compiler/lib/intel64:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH
After that, this is the kind of response I get from the terminal:
leonardo@Leonardo-linux:~$ which ifort
/opt/intel/composer_xe_2015.3.187/bin/intel64/ifort
leonardo@Leonardo-linux:~$ ifort -v
ifort version 15.0.3
leonardo@Leonardo-linux:~$ ifort
ifort: command line error: no files specified; for help type "ifort -help"
So it seems that things are OK, but they're not.
When I try this other command, this is what comes out of the terminal:
leonardo@Leonardo-linux:~/lib$ sudo make -f makefile
ifort -c -O2 -m64 -mcmodel=medium -fconvert=little-endian -frecord-marker=4 -I/lib/src/grib_api-1.13.1/include erf.f90
/bin/bash: ifort: command not found
make: *** [erf.o] Error 127
Can someone help me? Here's a snippet of the makefile:
HELL = /bin/bash MAIN = FLEXPART_IFORT # FC = ifort INCPATH = /lib/src/grib_api-1.13.1/include LIBPATH1 = /lib/src/grib_api-1.13.1/lib LIBPATH2 = /lib/jasper-1.900.1/lib LIBPATH3 = ~/root/opt/intel/composer_xe_2015.3.187/bin/intel64 #FFLAGS = -O3 -m64 -mcmodel=medium -fconvert=little-endian -frecord-marker=4 -I$(INCPATH) FFLAGS = -O2 -m64 -mcmodel=medium -fconvert=little-endian -frecord-marker=4 -I$(INCPATH) #FFLAGS = -fbounds-check -m64 -mcmodel=medium -fconvert=little-endian -frecord-marker=4 -I$(INCPATH) LDFLAGS = $(FFLAGS) -L$(LIBPATH3) -L$(LIBPATH2) -L$(LIBPATH1) -lgrib_api_f90 -lgrib_api -lm -ljasper # MODOBJS = \ par_mod.o com_mod.o \ OBJECTS = \ writeheader.o assignland.o\ $(MAIN): $(MODOBJS) $(OBJECTS) $(FC) *.o -o $(MAIN) $(LDFLAGS) $(OBJECTS): $(MODOBJS) %.o: %.f90 $(FC) -c $(FFLAGS) $< clean: rm *.o *.mod
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As you probably figured out, if you read the more comprehensible parts of the thread, your sudo command discards your path settings as well as taking away your ownership of any files it creates.
If you had a makefile including an install target requiring sudo (but not fort), normal usage would be
make .....
After that completes
sudo make install
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page