Compiler mm5 error

[gfast]

1linuxfedora 9 X86_64

2 Intel Core 2 Extreme QX6800

3intel Compiler 11.0.069

4configure.user set

# 3i2. PC_INTEL (LINUX/INTEL)
#-----------------------------------------------------------------------------
RUNTIME_SYSTEM = "linux"
FC = ifort
FCFLAGS = -I$(LIBINCLUDE) -O2 -tpp7 -pc 64 -convert big_endian -DDEC_ALPHA
CPP = /lib/cpp
CFLAGS = -O
CPPFLAGS = -I$(LIBINCLUDE)
LDOPTIONS = -i_dynamic -O2 -tpp7 -pc 64 convert big_endian
LOCAL_LIBRARIES =
MAKE = make -i -r

I have the some errors

ifort -c -I../../include -O2 -tpp7 -pc 64 -convert big_endian -DDEC_ALPHA addall.F
ifort: command line remark #10148: option '-tp' not supported
parame.incl(105): #warning: illegal token on preprocessor directive line.

make[316]: Entering directory `/home/dongfang/mm5/MM5intel/physics/radiation/cloud'
ar ru ../../../libutil.a lwrad.o swrad.o
make[316]: vfork: Resource temporarily unavailable make

[gfast]

/opt/intel/Compiler/11.0/069/bin/intel64/fortcom: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
ifort: error #10273: Fatal error in /opt/intel/Compiler/11.0/069/bin/intel64/fortcom, terminated by 0x7f
make[2]: [addall.o]

/opt/intel/Compiler/11.0/069/lib/intel64/libifcore.so.5

[TimP]

Quoting - gfast

FCFLAGS = -I$(LIBINCLUDE) -O2 -tpp7 -pc 64 -convert big_endian -DDEC_ALPHA
...
LDOPTIONS = -i_dynamic -O2 -tpp7 -pc 64 convert big_endian

ifort -c -I../../include -O2 -tpp7 -pc 64 -convert big_endian -DDEC_ALPHA addall.F
ifort: command line remark #10148: option '-tp' not supported
parame.incl(105): #warning: illegal token on preprocessor directive line.

DId you try omitting the obsolete and fixing mis-spelled options?

-tpp7, as the reference says, is not supported. The meaning, 7 years ago, was something like "optimize for P4, not P-III."

If you meant -pc64, that would be relevant only for 32-bit x87 code. Since you are running on x86_64, you probably want the intel64 compiler.

Without the leading "-", those keywords will likely be interpreted as file names.

You seem to be mixing options for Intel compilers of various eras, without reading any docs.

[gfast]

Quoting - tim18

DId you try omitting the obsolete and fixing mis-spelled options?

-tpp7, as the reference says, is not supported. The meaning, 7 years ago, was something like "optimize for P4, not P-III."

If you meant -pc64, that would be relevant only for 32-bit x87 code. Since you are running on x86_64, you probably want the intel64 compiler.

Without the leading "-", those keywords will likely be interpreted as file names.

You seem to be mixing options for Intel compilers of various eras, without reading any docs.

thanks tim18

I set encironment cariables in .bashrc and modify configure.user.

**************************************************************************************

.bashrc

source /opt/intel/Compiler/11.0/069/bin/ifortvars.sh intel64

*************************************************************************************

configure.user

*******************************************************************

RUNTIME_SYSTEM = "linux"
FC = ifort
FCFLAGS = -I$(LIBINCLUDE) -g -O3 -convert big_endian -DDEC_ALPHA
CPP = /lib/cpp
CFLAGS = -O
CPPFLAGS = -I$(LIBINCLUDE)
LDOPTIONS = -i_dynamic -g -O3 convert big_endian
LOCAL_LIBRARIES = -L/opt/intel/Compiler/11.0/074/lib/intel64
MAKE = make -i -r

**************************************************************************

Compile my program with the intel64 compiler. but there are some probloms.

ifort -c -I../../include -g -O3 -convert big_endian -DDEC_ALPHA addall.F
parame.incl(105): #warning: illegal token on preprocessor directive line.
addall.F(526): #warning: illegal token on preprocessor directive line.
/opt/intel/Compiler/11.0/069/bin/intel64/fortcom: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
ifort: error #10273: Fatal error in /opt/intel/Compiler/11.0/069/bin/intel64/fortcom, terminated by 0x7f
make[2]: [addall.o] ignore

and i check upcompiler view with ifort view.there is ome error.

******************************************************************

[dongfang@localhost ~]$ ifort view /opt/intel/Compiler/11.0/069/bin/intel64/fortcom: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

ifort: error #10273: Fatal error in /opt/intel/Compiler/11.0/069/bin/intel64/fortcom,terminated by 0x7f

************************************************************

but libstdc++.so.5 is located in "/opt/intel/Compiler/11.0/069/lib/intel64/libstdc++.so.5

So I think compiler bug or compiler is needed some settings.but i read guides and don't find some resolvent.

[TimP]

Quoting - gfast

[dongfang@localhost ~]$ ifort view /opt/intel/Compiler/11.0/069/bin/intel64/fortcom: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

ifort: error #10273: Fatal error in /opt/intel/Compiler/11.0/069/bin/intel64/fortcom,terminated by 0x7f

************************************************************

but libstdc++.so.5 is located in "/opt/intel/Compiler/11.0/069/lib/intel64/libstdc++.so.5

So I think compiler bug or compiler is needed some settings.but i read guides and don't find some resolvent.

When you use a linux Fortran compiler to link with C++ compiled functions requiring C++ STL, you must specify the C++ run time library explicitly, in this case by appending -lstdc++, same as g95 or gfortran require. Even if you consider this a bug, ifort will follow normal linux practice. libstdc++ is supplied by the g++ installation required to run ifort, not by any Intel compiler installation. I don't follow why you want it linked from the Intel compiler library directory, although that may happen, if you copied it there yourself.

If you were using ifort Windows, as libraries are required from the VC installation, C++ support libraries are available by default, and in fact it is impossible to use C99 features without falling into C++ mode (name mangling and all). ifort doesn't go so far in emulating the Microsoft environment on linux.

[gfast]

Quoting - tim18

When you use a linux Fortran compiler to link with C++ compiled functions requiring C++ STL, you must specify the C++ run time library explicitly, in this case by appending -lstdc++, same as g95 or gfortran require. Even if you consider this a bug, ifort will follow normal linux practice. libstdc++ is supplied by the g++ installation required to run ifort, not by any Intel compiler installation. I don't follow why you want it linked from the Intel compiler library directory, although that may happen, if you copied it there yourself.

If you were using ifort Windows, as libraries are required from the VC installation, C++ support libraries are available by default, and in fact it is impossible to use C99 features without falling into C++ mode (name mangling and all). ifort doesn't go so far in emulating the Microsoft environment on linux.

hello tim18

http://support.intel.com/support/cn/performancetools/sb/cs-026141.htm

i install compat-libstdc++ and compiler surccse.

Thanks your help I have one problom .I am chooceing equivalent compiler options

my cpu Intel Core2 Extreme Processor QX6800 (8M Cache, 2.93 GHz, 1066 MHz FSB)

[TimP]

Quoting - gfast

http://support.intel.com/support/cn/performancetools/sb/cs-026141.htm

i install compat-libstdc++ and compiler surccse.

Thanks your help I have one problom .I am chooceing equivalent compiler options

my cpu Intel Core2 Extreme Processor QX6800 (8M Cache, 2.93 GHz, 1066 MHz FSB)

As the 11.0 compiler for Intel64 is a native compiler, it doesn't need the 32-bit compat-libstdc++ required by the 10.1 compiler itself. Your combined Fortran and C++ project has to be entirely 64-bit objects and libraries as well. The 64-bit ld will ignore the contents of any 32-bit libraries you supply, but it will inherit the search paths which belong to 64-bit g++, appended to the paths which belong to 64-bit ifort. 32-bit g++ components are no longer needed for any part of the 64-bit development process. The presence of 1 or more 32-bit libraries in 11.0 Intel64 releases up through 11.0/069 appears to have been an error which was corrected in 11.0/074.