- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
I installed 10.6.2 and I am using the intel fortran compiler 11.0, when I compile my old
codes I get this error:
ld: in /opt/intel/Compiler/11.0/054/lib/libirc.a(proc_init.o), section not found for address 0x100000120
can you please help.
Thanks, Yassine
Link Copied
11 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please upgrade your Intel Fortran compilerfor Mac OS X to the latest 11.1 Update 4 (11.1.080). Snow Leopard support wasn't introduced until 11.1 Update 2 (11.1.067) and the specific issue you cite was addressed in the 11.1 Update 3 (11.1.067). See the previous discussion (here).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Kevin Davis (Intel)
Please upgrade your Intel Fortran compilerfor Mac OS X to the latest 11.1 Update 4 (11.1.080). Snow Leopard support wasn't introduced until 11.1 Update 2 (11.1.067) and the specific issue you cite was addressed in the 11.1 Update 3 (11.1.067). See the previous discussion (here).
Best
Y.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If your license did not expire before 11/30/2009 (the build date of the compiler in 11.1 Update 4 - see below) then you can still install the 11.1 Update 4.
$ ifort -V
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091130 Package ID: m_cprof_p_11.1.080
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Kevin Davis (Intel)
If your license did not expire before 11/30/2009 (the build date of the compiler in 11.1 Update 4 - see below) then you can still install the 11.1 Update 4.
$ ifort -V
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091130 Package ID: m_cprof_p_11.1.080
and lapack. I compiles the files in /interfaces/... I think I am missing something, should I link to libguide.a or libmkl_intel.a?
Regards
Y.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - yassineb
Thanks Kevin. My license expired before. I tried ifort -m32, it seems working but I have trouble to link with Blas
and lapack. I compiles the files in /interfaces/... I think I am missing something, should I link to libguide.a or libmkl_intel.a?
Regards
Y.
I used ifort -m32, it compiles but I have trouble to find the libraries
here what I get.
ifort -m32 -g -O i2dcom.o i2dquad.o i2dint.o i2df90.o twodexact.o deftype.o modcommon_provi.o modcommon.o utiles.o readfreq.o readgeom.o resol.o utiles_assemble.o source.o assemble_ef_iter.o assemble_ei_iter.o alloc.o cesc_precond.o assemblemass.o gmres.o iteration.o main_iter.o -o iterate /opt/intel/Compiler/11.0/054/Frameworks/mkl/lib/32/libmkl_intel.a /opt/intel/Compiler/11.0/054/Frameworks/mkl/lib/32/libmkl_core.a /opt/intel/Compiler/11.0/054/lib/libguide.a
Undefined symbols:
"_mkl_blas_zgemm", referenced from:
_mkl_lapack_zgetri in libmkl_core.a(zgetri.o)
"_mkl_lapack_zgetrf", referenced from:
_zgetrf_ in libmkl_intel.a(_zgetrf.o)
"_mkl_blas_ztrmm", referenced from:
_mkl_lapack_ztrtri in libmkl_core.a(ztrtri.o)
_mkl_lapack_ztrtri in libmkl_core.a(ztrtri.o)
"_mkl_blas_ztrsm", referenced from:
_mkl_lapack_zgetri in libmkl_core.a(zgetri.o)
_mkl_lapack_zgetrs in libmkl_core.a(zgetrs.o)
_mkl_lapack_zgetrs in libmkl_core.a(zgetrs.o)
_mkl_lapack_zgetrs in libmkl_core.a(zgetrs.o)
_mkl_lapack_zgetrs in libmkl_core.a(zgetrs.o)
_mkl_lapack_ztrtri in libmkl_core.a(ztrtri.o)
_mkl_lapack_ztrtri in libmkl_core.a(ztrtri.o)
ld: symbol(s) not found
make: *** [iterate] Error 1
Thanks
Y.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The link requires a bit more. Try consulting the MKL link advisor (here) for the proper command-line options for linking MKL libraries.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Kevin Davis (Intel)
The link requires a bit more. Try consulting the MKL link advisor (here) for the proper command-line options for linking MKL libraries.
11.0 works in leopard snow by just modifying ifort by ifort -m32. I will sure buy a new license to get 11.1 in the future.
Best
Y.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
-m32 is designed to invoke the 32-bit compiler. Without that I expect you were invoking the 64-bit compiler. You can see the compiler version details using the -V option.
I'm glad you found 11.0 w/-m32 works in your case, but I'm puzzled and others mileage may vary for trying the same. Official support for Snow Leopard was only provided in the 11.1 editions I noted earlier.
Curiously, I'mfinding the -m32/-m64 optionsare broken in 11.1 one of our systems.On yet another system, the options function as expected with 10.1, but not with 11.0 (11.1.066).
Could you do me a favor and execute the commands below on your system and paste the output into a reply?
ifort -V -m32
ifort -V -m64
You should see different compiler sign-ons similar to this:
$ ifort -V -m32
Intel Fortran Compiler Professional for applications running on IA-32, Version 11.0 Build 20090609 Package ID: m_cprof_p_11.0.066
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.
$ ifort -V -m64
Intel Fortran Compiler Professional for applications running on Intel 64, Version 11.0 Build 20090609 Package ID: m_cprof_p_11.0.066
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No need to run the earlier requested commands. Under the hood the correct compiler (fortcom) is invoked but the banner displayed by the ifort driver is incorrect in 11.1. This will be fixed in a future release.
$ ifort -V -m32 hello.f90 -#
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091130 Package ID: m_cprof_p_11.1.080
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.
/usr/bin/ifort-11.1-base/bin/ia32/fortcom
$ ifort -V -m64 hello.f90 -#
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091130 Package ID: m_cprof_p_11.1.080
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.
/usr/bin/ifort-11.1-base/bin/intel64/fortcom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Kevin Davis (Intel)
No need to run the earlier requested commands. Under the hood the correct compiler (fortcom) is invoked but the banner displayed by the ifort driver is incorrect in 11.1. This will be fixed in a future release.
$ ifort -V -m32 hello.f90 -#
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091130 Package ID: m_cprof_p_11.1.080
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.
/usr/bin/ifort-11.1-base/bin/ia32/fortcom
$ ifort -V -m64 hello.f90 -#
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091130 Package ID: m_cprof_p_11.1.080
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.
/usr/bin/ifort-11.1-base/bin/intel64/fortcom
I did it and I get that
ifort -V -m32
Intel Fortran Compiler Professional for applications running on Intel 64, Version 11.0 Build 20080930 Package ID: m_cprof_p_11.0.054
Copyright (C) 1985-2008 Intel Corporation. All rights reserved.
bash-3.2$ ifort -V -m64
Intel Fortran Compiler Professional for applications running on Intel 64, Version 11.0 Build 20080930 Package ID: m_cprof_p_11.0.054
Copyright (C) 1985-2008 Intel Corporation. All rights reserved.
Best
Y.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. That shows the confusion where it seems the same compiler is executed, but one can verify with the -# option that the correct fortcom is invoked. We apologize for the confusion.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page