OSX Lion complains icc 12.0 is trying to exclude Time Machine backups w/o root status

[Ronald_B_]

Title says it all. I just got the icc and ifort compilers installed, following a NIGHTMARE getting Xcode on, and a problem I've never seen before crops up: FIFTEEN error messages, all similar to

2011-08-10 08:47:11.591 icc[4048:60b] This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.

just from a bare invocation "icc" (no files!).

I found a discussion among Chromium developers: apparently this is not new with Lion, but also appeared in Snow Leopard. SHOULD icc have root access? I shiver at the thought of a compiler gone wild, with root priviliges.

Apple's reply in the Chromium thread was unyielding: it's documented, change your ways. Can Intel fix this, or provide a patch? I've not seen this behavior before, but I'm pretty sure I was using 11.1 before upgrading. I can send the warning messages to /dev/null, but I might miss some wheat with the chaff.

System: Apple Mac Pro 1.1, Lion freshly installed, Xcode 4.1.1, although I'm only using the command-line.
Fortran XEComposer and C XEComposer (or whatever they're called) for Mac OS X, version 12.0 of the compilers.

--Ron Bruck

--Ron Bruck

[Ron_Green]

I am thinking that the name 'icc' is clashing with some other program or application on your system. That error message is NOT an Intel compiler message.

do this:

which icc

or

icc -V

and did you:

source /opt/intel/bin/compilervars.sh intel64

And your compiler had better be 12.0 Update 5. We still do not officially support Lion until Update 6 in mid-september. However, I have 12.0 U5 working on my Lion testbed, so I'm not sure what it is you are seeing.

ron

[Steven_L_Intel1]

Actually, we do claim support for Lion in Update 5. I see the same behavior with Fortran on my Macbook, it's not a name conflict. Doesn't stop the compiler from working, though. Very odd. I am not a Mac expert.

[Steven_L_Intel1]

Our developers are looking into this now - the issue ID is DPD200171430. It appears to be coming from the license management code.

[Steven_L_Intel1]

One of our developers found that he could make the problem go away by invoking the compiler once with "sudo". Does that work for you?

[Ron_Green]

the sudo trick does not work for me, nor running ifort as root.

ron

[Steven_L_Intel1]

Another user said it worked for him. I will try this myself over the weekend.

[Jeffrey_A_Intel]

The fix for this problem should be available in the next update to the 12.1 compilers which is currently scheduled for February 2012.

[pbro1]

Confirming: Fixed in 12.1.4 20120423 (Update 10).

Whew. Finally I can actually look at compile output and see interesting stuff without having to filter out those irritating warnings.