Update for Intel Compilers on Leopard
By dgohara at Mon, Dec 10 2007 8:31am |
Intel has released a version of their compilers (C++ and Fortran) that appears to work properly on Mac OS X Leopard. The new distribution is labeled 10.1.007. You can download them from the Intel website using either oyur premier account (http://premier.intel.com or purchase them from the Intel website or third party sources. From my tests so far, this version appears to work for both the 32-bit and 64-bit versions of the compilers and Xcode support works as well.



Comments
Problems with locale and multibyte characters.
I am running into a problem with the 10.1 compilers on Leopard, whenever I try to run a configure script generated by automake. When I run the ./configure, on the first check of icc, the configure fails with the following error:
Catastrophic error: could not set locale "" to allow processing of multibyte charactersThis is true of every package I have tried to configure. An example of source code it is trying to compile is:
/* confdefs.h. */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE "libconfig"
#define VERSION "1.2"
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
If I copy this code into a file, and try compiling it on my own, it works fine. So I am guessing the configure script is doing something to upset icc. I have reported this problem to intel (about 2 weeks ago) and while they were eagerly trying to help for the first day, they dropped it. Has anyone else seen this? A workaround is to specify the compiler as "icc -no-multibyte-chars", but this is obviously not optimal. (Everything worked fine with the 10.0.x compilers). Any ideas?
Re: Problems with locale and multibyte characters.
I'm seeing the same thing with our Makefile based packages as well. The -no-multibyte-chars flag, allows it to proceed in my hands as well. It's not clear to me why that would work in this case, though.
Dave
idb fails!
Hi,
I'm using 10.5.1 with 10.1.007 but idb fails with this error message:
idb siesta
Intel(R) Debugger for applications running on Intel(R) 64, Version 33, Build 20071113
------------------
object file name: siesta
2007-11-12 12:01:51.311947: idb : in threadPortSetup(), task_get_exception_ports() failed
Assertion failed: !"Request-result mis-match!"src/appl/ctrl/controldefuxmac.C8786
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
Could not start process for siesta
No image loaded ... Recovering ...
(idb)
Of course siesta is the name of the program that I'm trying to debug.
Do you encounter the same problem?
Re: idb fails
I'm getting the exact same error as you. Although gdb on intel binaries seems to be working OK, so far.
Dave
idb fails indeed... and gdb too... and portland, and absoft!!
hi,
i am having the same error with idb:
MyMac: ~/INTEL-FORTRAN-BARCELONA-LAST #46 > idb testintel
Can't set locale. Using the C locale
Intel(R) Debugger for applications running on Intel(R) 64, Version 33, Build 20071113
------------------
object file name: testintel
2007-11-26 17:24:54.109802: idb : in threadPortSetup(), task_get_exception_ports() failed
Assertion failed: !"Request-result mis-match!"src/appl/ctrl/controldefuxmac.C8786
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
Could not start process for testintel
No image loaded ... Recovering ...
(idb)
i have been talking with Intel people through the support account i have. they are
nice, trying to see what´s going on. it is a real problem. i NEED a debugger to
program our monster code.
but i have to say that THERE IS NO DEBUGGER i have tried this three days that is
working properly!!! all of them give problems. gdb under gfortran crashes, portland
under pgf too. absoft is the only one that seems to work fine, but it gives no
values of variables passing through modules (geez... this is such an oooooold problem)
i copy here some of the errors i get:
MyMac: ~/INTEL-FORTRAN-BARCELONA-LAST #47 > gdb testgfor
GNU gdb 6.3.50-20050815 (Apple version gdb-768) (Tue Oct 2 04:07:49 UTC 2007)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin"...
warning: Unable to read symbols for "/usr/local/lib/libgfortran.3.dylib" (file not found).
Reading symbols for shared libraries ... done
warning: Could not find object file "/var/folders/CS/CSfpm18UFH0uNathfGkYKU+++TI/-Tmp-//ccgceHrc.o" - no debug information available for "test.f90".
(gdb)
and
MyMac: ~/INTEL-FORTRAN-BARCELONA-LAST #50 > pgdbg -text testpgi
NOTE: your trial license will expire in 13 days, 6.39 hours.
PGDBG 7.0-7 x86-64 (Workstation, 4 CPU)
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2007, STMicroelectronics, Inc. All Rights Reserved.
warning: unable to open object file '/var/folders/CS/CSfpm18UFH0uNathfGkYKU+++TI/-Tmp-/pgf95CPturrKw56b.o'
Loaded: /Users/mariano/INTEL-FORTRAN-BARCELONA-LAST/testpgi
ERROR: No target selected.
NOTE: Can't find main function compiled -g
pgdbg>
my hands are tight...
jzz
fortran debuggers in leopard... getting worse!
well, well, well...
see the answer absoft support gave to me about printing variables passing through
modules..
"Hello,
"
"This issue has to do with Apple's debug information. Debuggers are not able to read "this information because Apple has not fixed this issue with the debug information. "Unfortunately, there is nothing more we can do to get this issue fixed. We have
"issued "the a bug report with Apple. Sorry, I could not be more helpful.
i am getting a bit upset...
jzz
have the debuggers been fixed
Has there been any headway with getting the debuggers working under Mac OS X? I have been working on fairly complicated piece of Fortran code (F95) and would like to use a debugger to step through the program and find the source of some mysterious runtime errors.
intel debugger smoothly working
intel debugger is now working very well... "very well" means as well as in any linux or windows, at least for our f95 application, which is rather complicated indeed.
this has taken many iterations with intel people (nice people).
but it seems that major problems has been solved
Intel Debugger in xcode
While in this subject, I haven't been able to use idb as the debbuger in xcode. Has anyone been able to do this? I'm using Xcode 3.0 in 10.5.2.
Thanks. Andrés
tutorial of IDB in Xcode 3
If IDB 10.1 works in Xcode, does anyone know of a good tutorial on how to set it up and use it to debug F95? I use a make file.
New PGDBG Available
An update to PGDBG (7.2-4) is available that should address the problems cited. PGDBG now supports debugging OpenMP parallel applications on both Leopard and Tiger.