Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29277 Discussions

ifort: error #10149: option '-cxxlib-gcc' not supported with the current installed GCC

jaminkoo
Beginner
1,243 Views
I have been using ifort for several months. But today I ran into this issue.

ifort: error #10001: could not find directory in which g++ resides

So I looked it up and set GXX_ROOT to:
setenv GXX_ROOT /usr/lib/gcc/x86_64-redhat-linux/4.1.2/

Then I am getting a different error.
ifort: error #10149: option '-cxxlib-gcc' not supported with the current installed GCC

$ ifort -V
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.0 Build 20080930 Package ID: l_cprof_p_11.0.069
Copyright (C) 1985-2008 Intel Corporation. All rights reserved.

$ gcc --version
gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ g++ --version
g++ (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

0 Kudos
5 Replies
TimP
Honored Contributor III
1,243 Views
If you have cxxlib-gcc in your ifort command, you should remove it. There never was a cxxlib-icc option in the x86_64 compilers, so the acceptance of the option string has been removed. cxxlib-gcc simply means that if you call any C++ STL functions, the Dinkumware library won't be used, even if it is available.
Normally, you would have your PATH and LD_LIBRARY_PATH set so that g++ is working, as a prerequisite to using ifort.
0 Kudos
jaminkoo
Beginner
1,243 Views
Thanks for your answer.
I actually just resolved it now, but I am not sure how it is related to the error message.

I just had to clear /tmp directory. It was full.
When I tried compiling something with gcc, it complained that /tmp was full.
0 Kudos
TimP
Honored Contributor III
1,243 Views
So it selected the wrong error message for the case of full /tmp ?
0 Kudos
jaminkoo
Beginner
1,243 Views
Yes.
after removing files from /tmp, it worked fine.
0 Kudos
Xiaoping_D_Intel
Employee
1,243 Views
There is a KB article about this error - http://software.intel.com/en-us/articles/cdiag10149/

A possible reason in this case is that full /tmp path causes g++ fail to run and make ifort mistake g++ not accessible by the user account.
0 Kudos
Reply