idb did not install with ifort evaluation

[Mike_Mills]

I've just installed a 30-day evaluation of ifort 11.1 for Mac OS X, and the debugger idb is missing. I tried also installing the C compiler, but that also is missing the idb debugger. How do I go about evaluating the debugger? I am running Mac OS 10.6.

[Ron_Green]

Quoting - millscolorado.edu

I've just installed a 30-day evaluation of ifort 11.1 for Mac OS X, and the debugger idb is missing. I tried also installing the C compiler, but that also is missing the idb debugger. How do I go about evaluating the debugger? I am running Mac OS 10.6.

idb should be installed in /opt/intel/Compiler/11.1//bin/idb

Did you:

source /opt/intel/Compiler/11.1/058/bin/ifortvars.sh intel64 [or ia32 if you have an older 32bit Mac]

so that your paths are set up properly?

ron

[Mike_Mills]

Quoting - Ronald W. Green (Intel)

idb should be installed in /opt/intel/Compiler/11.1//bin/idb

Did you:

source /opt/intel/Compiler/11.1/058/bin/ifortvars.sh intel64 [or ia32 if you have an older 32bit Mac]

so that your paths are set up properly?

ron

I do not have idb in that path, nor in the subpaths intel64 and ia32. I have sourced the intel64/ifortvars.sh so that my path is set up properly.See shell session below:

=-=-=-

Tillamook:~ 500$ cd /opt/intel/Compiler/11.1/058/bin/

Tillamook:bin 501$ ls

ia32 iccvars.sh ifortvars.sh

iccvars.csh ifortvars.csh intel64

Tillamook:bin 502$ cd intel64

Tillamook:intel64 503$ ls

codecov icpc.cfg profmerge

codecov_libFNP.dylib icpc_libFNP.dylib proforder

fortcom ifort svcpcom

fpp ifort.cfg svfortcom

icc ifort_libFNP.dylib tselect

icc.cfg ifortvars_intel64.csh tselect_libFNP.dylib

icc_libFNP.dylib ifortvars_intel64.sh xiar

iccvars_intel64.csh mcpcom xild

iccvars_intel64.sh prelink xilibtool

icpc profdcg

Tillamook:intel64 504$ pwd

/opt/intel/Compiler/11.1/058/bin/intel64

Tillamook:intel64 505$ cd ../ia32/

Tillamook:ia32 506$ ls

codecov icpc.cfg profmerge

codecov_libFNP.dylib icpc_libFNP.dylib proforder

fortcom ifort svcpcom

fpp ifort.cfg svfortcom

icc ifort_libFNP.dylib tselect

icc.cfg ifortvars_ia32.csh tselect_libFNP.dylib

icc_libFNP.dylib ifortvars_ia32.sh xiar

iccvars_ia32.csh mcpcom xild

iccvars_ia32.sh prelink xilibtool

icpc profdcg

Tillamook:ia32 507$ which idb

Tillamook:ia32 508$ echo $PATH

.:/Users/mills/usr/local/bin:/Volumes/Data/Libraries/mpich/bin:/Users/mills/usr/ncl/bin:/Volumes/Data/Libraries/netcdf/bin:/opt/intel/Compiler/11.1/058/bin/intel64:/opt/local/bin:/opt/local/sbin:/sw/bin:/sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/X11R6/bin:/Applications/itt/idl/bin

=-=-=-=

Would it affect the installation that I have a licensed copy of 10.1.014 installed? I wouldn't think so. I do have that version of idb in/opt/intel/idbe/10.1.014/bin

[Mike_Mills]

I just tried moving the whole /opt/intel directory to /opt/intel2, then reinstalled ifort. It created a new /opt/intel directory, but I still do not have idb.

[Ron_Green]

Quoting - Mike Mills

I just tried moving the whole /opt/intel directory to /opt/intel2, then reinstalled ifort. It created a new /opt/intel directory, but I still do not have idb.

Mike,

I apologize, I just now noticed that you are running Snow Leopard. Intel won't support Snow Leopard until we release our next version of the 11.1 compiler. This will occur sometime around mid-September.

It would be helpful to know the hardware specifics for your Mac. Is this an iMac, Mac Pro, MacBook or MacBook Pro? If iMac, approximately when did you purchase the computer? What processor name, and what processor speed (from 'About this Mac' from the Apple Menu)

Oh, and did you do a standard installation or a custom installation?


thanks

ron

[Mike_Mills]

Thanks, Ron. I'm running on a 2009 Mac Pro with 2 x 2.93 GHz Quad-Core Intel Xeon "Nehalem" processors. I did a standard installation for ifort and C++. I looked at the custom installation options, but didn't see anything additional that could be added.

[Quoc-An_L_Intel]

Quoting - Mike Mills

Thanks, Ron. I'm running on a 2009 Mac Pro with 2 x 2.93 GHz Quad-Core Intel Xeon "Nehalem" processors. I did a standard installation for ifort and C++. I looked at the custom installation options, but didn't see anything additional that could be added.

What are you getting as a return value for the command: "sysctl hw.cpufamily", as well as "sysctl hw.machine"?

An

[Mike_Mills]

Quoting - Qale (Intel)

What are you getting as a return value for the command: "sysctl hw.cpufamily", as well as "sysctl hw.machine"?

An

hw.cpufamily: 1801080018

hw.machine: i386

[Ron_Green]

Quoting - Mike Mills

hw.cpufamily: 1801080018

hw.machine: i386

Mike,

We are investigating this on our Mac Pro Nehalem system.

Hopefully this is the last question we'll ask: are you using a released version of Snow Leopard or a beta version?

Sorry to keep dragging this on, but we'd like to fully understand the environment you have. It will help us and help other users.

ron

[Mike_Mills]

No problem, Ron. I'm happy to answer any questions you have to help sort this out.

I'm using the released version of Snow Leopard.

[Quoc-An_L_Intel]

This is a known problem, and it will be fixed in the next update. Thanks for notifying us.

http://software.intel.com/en-us/articles/intelr-debugger-failed-to-install-on-mac-pro-with-quad-core-intel-xeon-processor/

In the mean time, if you want a work around,


1) mount the image .dmg file
2) copy directory /Volumes/m_cprof_p_11.1.058/m_cproc_p_11.1.058.mpkg to a local directory
3) modify m_cprof_p_11.1.058.mpkg/Contents/distribution.dist to check for Nehalem signature Line #210 (see red below)
4) double click on the local m_cprof_p_11.1.058.mpkg and restart the installation


function determine_Arch32_64() {
var result = false;
try {
// this next line checks for the intel64 bit cpufamily
result = system.sysctl('hw.cpufamily');
if(result == 1114597871 || result == 2028621756 || result == 1943433984 || result == 1801080018) {
result = true;
}
else {
result = false;
}
} catch (e) {}


return result;
}