Fortran Compiler on Mac Pro questions

[postaquestion]

Hello, I'm trying to install an Evaluation Copy of your Fortran compiler. The installer allows entry of the evaluation serial number, and approval of the license agreement, but then when it asks for the user to select the destination drive for the installation, there is no hard drive to select in the installation GUI.

Normally in such installation programs, all of the available drives are shown, but that's not the case here. So, there's no option to continue past that point, and the GUI just finishes without installing. We tried this both in a regular User account and in an Administrator account. The machine is an Intel Mac Pro running Leopard.

Can you please offer advice for circumventing this problem? I am very much interested in buying this compiler but need to evaluate it first.

[Ron_Green]

I can't reproduce what you're seeing. I downloaded m_fc_p_10.1.014 from the eval site.

I'm using Leopard 10.5.2, Xcode 3.0

On the 'Select a Destination' screen - does it show NO disks, or does it show 'Macintosh HD' with a read alert and exclamation mark?

How much disk space do you have free? By default, it will try /opt for the installation area. You did say you tried as an Admin user, yes?

If none of this helps, go to http://premier.intel.com and open an issue.

ron

[tmbrown]

On the 'Select a Destination' screen, the installer shows no disks. It does not show 'Macintosh HD' with an alert or anything like that.

The machine has 3 internal HDs. The first has 179 GB free, the second has 466 GB free, and the third has 186G free.

We've installed a lot of software on this machine already, and so far the installer for each one has shown the expected dialog at the 'Select a Destination' screen (i.e., a choice of HDs) and then successfully installed the software.

Yes, this was tried as an Admin user.

Unfortunately, I emailed Intel Tech support already, and they are the ones that put my question on this forum. We are currently upgrading our facility to Leopard, and trying to decide between AbSoft, NAG, and Intel Fortran compilers. We were leaning toward Intel before this incident (based on previous performance), but this is now looking like Intel is out of the running, since we can't even evaluate it and have not received any suggestions from Tech Support for possible solutions.

Thanks for your reply.

[Steven_L_Intel1]

Sorry to hear about the problem you had with support. That's not normal. Were you given a six-digit case number? If so, what was it? I'll try to get you connected.

[tmbrown]

No, I was not given a 6-digit case number. Perhaps this is because I only have an evaluation copy so far? When I signed up for the evaluation copy, Intel sent an email with the evaluation license number and a URL for tech support. When it did not install, I contacted tech support by that link, and got a response from Gina B. at isn.support@intel.com, giving me a "thread ID" but no case number. When I replied to her, she suggested I contact Intel Registration Support at a URL with "Self Help" in the address, which doesn't sound too promising, either.

[mdmaeyer]

I here in Belgium have exactly the same problem. I asked and obtained an evaluation key. installed Xcode on MacOSX Leopard on a powerbook pro.and installed the fortran compiler (the installer comes bach after less than a second)
Nothing installs in /opt/....

I have send a message to support but no answer yet.

I wanted to switch from Absoft, since each time they release a new version, I had to change my existing code. The optimizer does not seem to be great. (I have also used IBM fortran copiler, this was great but is not supported anymore)

[Steven_L_Intel1]

tmbrown, I understand now what happened. You must have clicked on the Feedback link in this forum. That goes to the people who manage this forum, not compiler technical support. The email you received with the evaluation should have given you directions for tech support. You could also click the "Tech Support" link towards the top of the forum home page (the one with a list of topics.) This will take you to the support page for the Mac compiler and there you'll find instructions on how to ask for tech support.

You will need to register your serial number first, then you will have full access to Intel Support for the duration of your evaluation period. Please follow the link above for more information. If you get stuck, you can ask here and we'll help you out.

[Steven_L_Intel1]

mdmaeyer, thanks for reporting the problem. I'll check up on this to see what the situation is. It is not a symptom I am familiar with.

[Ron_Green]

mdmaeyer - Do you have a "Powerbook Pro" (Power PC based) or a MacBook Pro (Intel based)? The Intel compiler only supports computers with Intel processors. This might be why the installer died immediately - it is an Intel-architecture binary and will not run on PowerPC.

Please let us know.

Thank You.

ron

[Ron_Green]

tmbrown - I can ask our installer team what could cause it to not recognize the disks. First, your Mac Pro - did you purchase this before Jan 2008: in other words, is it the latest Mac Pro or the original Mac Pro with Woodcrest (dual core) or Clovertown (quad core) processors build before Jan 2008?

And then, what version of Mac OS X are you running ( 10.5.x or 10.4.x , where I need the "x" number also). Also, are you using the English language or a foreign language for your interface?

Do you launch the installer by clicking the icon in the disk image folder, or do you launch from command line? If command line, do you use 'sudo'?

Is there anything unusual about your disks I should know?

This is the first report of such a problem, and as I said, I can't reproduce what you are seeing.

[mdmaeyer]

Of course an Intel Powermacbook pro. Thanks

[mdmaeyer]

Here my configuration;
Model Name: MacBook Pro 17"
Model Identifier: MacBookPro2,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.33 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 667 MHz

[Ron_Green]

tbbrown - as a possible work around, mount the dmg image. Open the 'INSTALL.htm' document. The second half of this document has the 'silent install' procedure. This is for a command-line installation. Please try this.

And of course, we're curious to know the results.

thanks

ron

[mdmaeyer]

ok Ron, I did several things:

First I tried the cp -pP /Volumes...
This failed because I can not write --> so I used first with sudo cp
This worked.

There is a typo error in stead of ./si_sicore it should be ./secore (but thats an easy one)

so I started after the export command:
xport DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.014/instman:$DYLD_LIBRARY_PATH

QUESTION do i leave the $DYLD_LIBRARY_PATH or do I have to replace it with the actual path??

I proceeded see the output (first just ./si_secore but this gave errors then with the sudo command which also gave errors.

There is some progress.
Here the output of the screen:

bash-3.2$ ./si_secore

----------------------------------------------------------------------
USAGE...
./si_secore -sn "cccc-xxxxxxxxx"
./si_secore -c "config file"
./si_secore -licfile "lic file"
./si_secore -c "config file"
./si_secore -c "config file" -sn "cccc-xxxxxxxxx"
./si_secore -c "config file" -licfile "lic file"

exiting...
----------------------------------------------------------------------
bash-3.2$ ./si_secore -n VWBF-8H4WV5GT

read media config file:./mediaconfig.xml
code name:FCompM
disp name:Intel Fortran Compiler 10.1 for Mac OS* X
platform:MacOS
version:10.1
serial number:VWBF-8H4WV5GT
read config file:./si_issa.xml
sn:
license file:
Proxy host:xxxxx
Proxy port:0
first name:xxx
last name:xxxx
country:US
company:ccccccc
email:xxxxxxxx@yy.xx

install with serial number option...
serial number:VWBF-8H4WV5GT
serial number:VWBF-8H4WV5GT is registered
installing Tool[1]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idb_10.1.014.pkg
--------------------------------------------------
/Users/m_fc_p_10.1.014/instman/../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idb_10.1.014.pkg
installer: This package requires authentication to install.

--------------------------------------------------

installing Tool[2]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idbe_10.1.014.pkg
--------------------------------------------------
/Users/m_fc_p_10.1.014/instman/../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idbe_10.1.014.pkg

installer: This package requires authentication to install.

--------------------------------------------------

installing Tool[3]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/ifort_10.1.014.pkg
--------------------------------------------------
installer: This package requires authentication to install.

--------------------------------------------------

installing Tool[4]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/iforte_10.1.014.pkg
--------------------------------------------------
installer: This package requires authentication to install.

--------------------------------------------------

done.....


bash-3.2$ sudo ./si_secore -n VWBF-8H4WV5GT
dyld: Library not loaded: /Users/mslrepos/pkolur/issa_build070307/Project/Development/ThirdParty/Xerces/xerces-c-src1_7_0_singlethreaded/lib/libxerces-c1_7_0.dylib
Referenced from: /Users/m_f c_p_10.1.014/instman/./si_secore
Reason: image not found
Trace/BPT trap

[Ron_Green]

The process spawned by sudo does not inherit the DYLD_LIBRARY_PATH. I have a document in the works to append/modify to the current silent install procedure. This should help.


Silent Install Using sudo
Users utilizing the sudo command to perform a silent install need to modify the above procedure. By default, sudo will not preserve the users DYLD_LIBRARY_PATH setting. The following silent install procedure should be used by sudo users:

To install the compiler with sudo in the "silent" mode with an interactive shell
1. Mount the product dmg file with required content using Finder, for example, by double-clicking on the dmg file.
2. Start a Terminal program from the Utilities group.
3. Using Terminal do the following:
a. Copy the contents of the mounted image to a local folder, for example
cp -pR /Volumes/m_fc_p_10.1.00x /Users/m_fc_p_10.1.0xx
b. Change directory to the local instman folder inside the folder you copied in (a), for example:
cd /Users/m_fc_p_10.1.00x/instman
c. Start a shell session under bash, for example:
sudo /bin/bash
d. Export DYLD_LIBRARY_PATH=, for example:
export DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
e. (optional) Make changes to si_issa.xml configuration file to change the default settings, see details below.
f. Run ./si_sicore with options as described above.

To install the compiler with sudo in the "silent" mode with minimal interaction
The following method uses sudo in a mode suitable for scripted automation.
1. Start a Terminal program from the Utilities, or create a user shell (rsh, X11, etc)

2. Change directories to a working area where the user has write permission. For example,

cd /Users/

where this is the home directory of user . This example assumes the user has downloaded or copied the compiler disk image (.dmg) file to this user home directory /Users//m_fc_p_10.1.0xx.dmg where 0xx is the compiler minor version.

3. Mount the compiler disk image. Assumes compiler .dmg file is in your current directory. This command will mount the compiler installer disk image under /Volumes/m_fc_p_10.1.0xx

sudo hdid m_fc_p_10.1.0xx.dmg

4. Copy the contents of the mounted image to a local folder where you have write permission. For example, if your current directory is user writeable:

cp -pR /Volumes/m_fc_p_10.1.0xx /Users/

again, where is replaced by your login or user name.

5. Change directories to /Users//m_fc_p_10.1.0xx/instman created by the previous copy command:

cd /Users//m_fc_p_10.1.0xx/instman

6. Use sudo to run the installer, using one of two possible methods:

a. sudo env DYLD_LIBRARY_PATH=/Users//m_fc_p_10.1.0xx/instman ./si_secore

b. sudo c DYLD_LIBRARY_PATH=/Users//m_fc_p_10.1.0xx/instman ; ./si_secore

where are replaced by si_secore options described above. For example, to use the serial number XXXX-XXXXXX to install:

sudo c DYLD_LIBRARY_PATH=/Users//m_fc_p_10.1.0xx/instman ; ./si_secore n XXXX-XXXXXX

7. (optional) Remove the compiler installation files. For example,

cd /Users/
rm Rf m_fc_p_10.1.0xx

8. (optional) Unmount the compiler installation image. For example,

sudo udiutil unmount /Volumes/m_fc_p_10.1.0xx

Finally, to truly make this sequence suitable for scripting, you can pass your password to the sudo commands above using the S option to sudo. For example,

echo MyPassword | sudo S
where MyPassword is your user password used to run sudo command.

[mdmaeyer]

Thanks Ron, I still get other problems now: bash-3.2# export DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.014/instman bash-3.2# ./si_secore -n xxxx-xxxxxxxx read media config file:./mediaconfig.xml code name:FCompM disp name:Intel Fortran Compiler 10.1 for Mac OS* X platform:MacOS version:10.1 serial number:xxxx-xxxxxxxx read config file:./si_issa.xml sn: license file: Proxy host:xxxxx Proxy port:0 first name:xxx last name:xxxx country:US company:ccccccc email:xxxxxxxx@yy.xx install with serial number option... serial number:xxxx-xxxxxxxx serial number:xxxx-xxxxxxxx is registered installing Tool[1]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idb_10.1.014.pkg -------------------------------------------------- /Users/m_fc_p_10.1.014/instman/../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idb_10.1.014.pkg installer: Error - This package can not be installed on this architecture. -------------------------------------------------- installing Tool[2]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idbe_10.1.014.pkg -------------------------------------------------- /Users/m_fc_p_10.1.014/instman/../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idbe_10.1.014.pkg installer: Error trying to locate volume at /opt/intel -------------------------------------------------- installing Tool[3]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/ifort_10.1.014.pkg -------------------------------------------------- installer: Error trying to locate volume at /opt/intel -------------------------------------------------- installing Tool[4]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/iforte_10.1.014.pkg -------------------------------------------------- installer: Error trying to locate volume at /opt/intel -------------------------------------------------- done.....

[Ron_Green]

The idb and idbe packages are a known bug in our installer that is being worked. This affects customers with the new "Penryn" based Macs that started shipping recently. This must be a fairly new Mac. I believe we have a workaround for those packages, let me check my database.

Now, the compiler packages. These are complaining about /opt/intel directory access. I've seen this when a user gets a new Mac and during the initial setup copy their old data from an older Mac. Did you do this? Did you copy your data onto the new Mac during setup? If so, what I've seen in the past is that /opt is a symbolic link to a non-existent disk or directory. To check this, try this:

ls -ld /opt

Is /opt a link, and is the target of that link valid and writeable? If not, remove the link and try again.

If opt is not there, try this:
sudo bash
touch /opt
touch /opt/intel

did this succeed?

ron

[mdmaeyer]

Hi Ron,

The directory /opt is there.
drwxr-xr-x@ 5 root admin 170 Sep 11 2007 opt

Indeed I copied my previous contents of my mac onto this. But recenty upgraded to leopard and reinstalled XTools v3.

This mac is around 1 year old.

regards,
Marc

[mdmaeyer]

Hi Ron,

Some progress when I did the following:

As you may notice all but the first Tool[1] succeeded. So only one hurdle to take.

I created the directory (as root) /opt/intel

sudo bash
export DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.014/instman

bash-3.2# ./si_secore -n VWBF-8H4WV5GT

read media config file:./mediaconfig.xml
code name:FCompM
disp name:Intel Fortran Compiler 10.1 for Mac OS* X
platform:MacOS
version:10.1
serial number:VWBF-8H4WV5GT
read config file:./si_issa.xml
sn:
license file:
Proxy host:xxxxx
Proxy port:0
first name:xxx
last name:xxxx
country:US
company:ccccccc
email:xxxxxxxx@yy.xx

install with serial number option...
serial number:VWBF-8H4WV5GT
serial number:VWBF-8H4WV5GT is registered
installing Tool[1]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idb_10.1.014.pkg
--------------------------------------------------
/Users/m_fc_p_10.1.014/instman/../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idb_10.1.014.pkg
installer: Error - This package can not be installed on this architecture.

--------------------------------------------------

installing Tool[2]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idbe_10.1.014.pkg
--------------------------------------------------
/Users/m_fc_p_10.1.014/instman/../setup/dist_fc_10.1.014.mpkg/Contents/Packages/idbe_10.1.014.pkg

installer: Package name is Intel Debugger 10.1 for Mac OS* X
installer: Installing at base path /
installer: The install was successful.

--------------------------------------------------

installing Tool[3]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/ifort_10.1.014.pkg
--------------------------------------------------
installer: Package name is Intel Fortran Compiler 10.1 for Mac OS* X
installer: Installing at base path /
installer: The install was successful.

--------------------------------------------------

installing Tool[4]:../setup/dist_fc_10.1.014.mpkg/Contents/Packages/iforte_10.1.014.pkg
--------------------------------------------------
installer: Package name is Intel Fortran Compiler 10.1 for Mac OS* X
installer: Installing at base path /
installer: The install was successful.

--------------------------------------------------

[Ron_Green]

Excellent! You are finished. The package that failed: there are 2 Intel debugger packages for Mac OS X: idb and idbe. The idb package that failed is strictly a 32bit debugger and is only installed on older Core Duo or Core Solo machines (those are 32bit CPUs). The idbe package is the 32- AND 64-bit Intel debugger. This package is installed on all 64 bit hardware, such as yours. So it is expected that the idb package would fail to install.

I'll work with our documentation folks to beef up the section on installation using sudo. For some reason we see a lot of users using sudo on Mac OS compared to Linux.

ron

[tmbrown]

Just to close the loop on the problem I had here, in case it helps anyone else:

I Googled the generic problem of GUI software installers not seeing a destination under Leopard (even though I had no problem installing other software). Some users found that quitting the installation, opening Disk Utility, and then restarting the installation GUI did the trick, although it sometimes takes Disk Utility a few minutes to recognize the drives when the machine is in this funny state of not finding its drives.

Disk Utility was not allowing the drives to be visible, either (even after we waited 15 minutes and even though we could manipulate the drives in Finder and on the command line). So, we tried disabling software that monitored the S.M.A.R.T. Status of the internal drives, restarted Disk Utility, saw the drives, restarted the Intel Installation, and it all worked fine.

In the end this was apparently more of a Leopard issue than anything else, although I still do not know why the Intel software was the only installation that failed out of many packages installed.