permissions during installation of evaluation package.

[Peter_Petropoulos]

Some time ago I downloaded the evaluation package for v.11.1.080 but
have been unable to install it on my mac laptop running Snow Leopard
10.6.2 (I've got latest xcode and X11 already there, along with macports
for the usual unix freeware).

The installer does not ask me for my root password and
instead gives me the following:

>Error while executing the startup script.
>Make sure that you have write permissions to /tmp,
>/Users/Shared/Library/Application Support/ and it's sub folders

However, /tmp is writable by me (other programs use it) and
I don't think anyone other than root should have permissions
to /Users/Shared/Library/Application Support/ and it's sub folders.

Any help greatly appreciated !

Thanks,
Peter

[Ron_Green]

Quoting - Peter Petropoulos

Some time ago I downloaded the evaluation package for v.11.1.080 but
have been unable to install it on my mac laptop running Snow Leopard
10.6.2 (I've got latest xcode and X11 already there, along with macports
for the usual unix freeware).

The installer does not ask me for my root password and
instead gives me the following:

>Error while executing the startup script.
>Make sure that you have write permissions to /tmp,
>/Users/Shared/Library/Application Support/ and it's sub folders

However, /tmp is writable by me (other programs use it) and
I don't think anyone other than root should have permissions
to /Users/Shared/Library/Application Support/ and it's sub folders.

Any help greatly appreciated !

Thanks,
Peter

Peter,

You will need to open up permissions to /Users/Shared/Library/Application Support. The license will need to be installed in /Users/Shared/Library/Application Support/Intel/Licenses.

I would argue that a path names "Users/Shared" should be writeable. Typically it is world-writeable after a fresh installation. After that, some software installations from other vendors are known to make that path read-only after they install.

If the intent was to make this only writeable by root, shouldn't the name be "Root/Unshared/..." :)

ron

[Peter_Petropoulos]

Quoting - Ronald W. Green (Intel)

If the intent was to make this only writeable by root, shouldn't the name be "Root/Unshared/..." :)

ron

Thanks Ron. I'm set now...

my intent has been satisfied :-) Apple's on the other hand, I don't know !

Peter

[Joseph_W_]

I am having the same problems with "Run Script Error - Error while executing the startup script. Make sure that you have write permissions to /tmp folder and /Users/Shared/Library/Application Support/Intel/Licenses folder"

This comes up everytime I attempt to open the software. 

Please can someone in simple terms explain how to install it so I can use it?

Many Thanks, 

Joseph 

[Jason_A_]

I had the same problem today, root owned the Library.  So I did a "sudo chown -R my_user_name /Users/Shared/Library" and it worked. 

[florian_b_2]

Hi 

I had the same problem but the command suggested above

"sudo chown -R my_user_name /Users/Shared/Library"

did not solve the problem. So I did "sudo chmod 777 /Users/Shared/Library"

that solved the problem described above. But now I get another error message directly after agreeing to the terms of the software licence agreement

Packaging error, Aborting the install.

are these problems related???

thanks

fl

[Casey]

Changing permissions like that defeates the purpose of having them and opens you up to potential malware threats that would otherwise not have access to system components.

Do something like "sudo bash" to open up a root shell, and do your installation from there.  That way you are installing the compiler as root, there will be no permission issues since you are root, and you wont be creating security problems by making your large portions of your system writable by anyone.  Just my 2c.

[bash]sudo bash[/bash]