Silent Installation Guide for Intel Compilers for Mac OS* X Versions 14.x, 13.x, 12.x, 11.x, 11.x and 10.1
As a rule, all product lines (except iMac) changed names when Apple made the switch: iBooks PowerBooks-MacBook Pro Power Mac chip model/speed - Mac Pro The iMac branding was retained, but the model year or System Info will sort it out. Mac OS X ISO DVD is very safe download if you have any question on this software please contact THE TECH SHOP 715-446-4333 or [email protected]. Testing conducted by Apple in June 2020 on production 1.4GHz quad-core Intel Core i5-based 13-inch MacBook Pro systems with 8GB RAM, 256GB SSD, and prerelease macOS Big Sur. Systems tested with WPA2 Wi-Fi network connection while running on battery power, with display brightness set to 12 clicks from bottom or 75%. Explore the world of Mac. Check out MacBook Pro, iMac Pro, MacBook Air, iMac, and more. Visit the Apple site to learn, buy, and get support.
Navigation
Linux and Mac OS X Compilers Installation Help Center: /en-us/articles/intel-compilers-linux-installation-help
This guide presents silent installation instructions for current and previous versions of Intel compilers. Newer compilers are described first, scroll down for version 11.x or older.
Silent Installation Guide for Intel Compilers for Mac OS* X Versions 14.x, 13.x, and 12.x
Here are the steps you need to follow to install the Intel Composer XE for OS X* version 2013 SP1 aka '14.0' in silent mode.
Step 0) Confirm that the userID for the installation has 'sudo' priviledge. If you are unfamiliar with the 'sudo' command please research that command on the internet to become familiar with it's use. Test your sudo priviledge with a simple sudo command such as 'sudo pwd' or 'sudo ls -l'
Step 0) Confirm that the userID for the installation has 'sudo' priviledge. If you are unfamiliar with the 'sudo' command please research that command on the internet to become familiar with it's use. Test your sudo priviledge with a simple sudo command such as 'sudo pwd' or 'sudo ls -l'
Step 1) Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. OR If you are working from a terminal window, use the hdiutil command to mount the compiler installer disk image (.dmg)
2013 SP1 Example:
2013 SP1 Example:
Disk image mounts under
- /Volumes/m_fcompxe_2013_sp1.u.vvv (for the Fortran Composer XE 2013 SP1)
- /Volumes/m_ccompxe_2013_sp1.u.vvv (for the C++ Composer XE 2013 SP1)
Mount the image
- sudo hdiutil attach m_fcompxe_2013_sp1.u.vvv.dmg
- sudo hdiutil attach m_ccompxe_2013_sp1.u.vvv.dmg
where 'u' is the update number ( 0, 1, 2, 3, etc) and where 'vvv' is the specific version ( 2013_sp1.2.142 is Update 2, version 142 for example)
Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already.
Step 3) Using 'Terminal', change directory to the /Packages folder:
Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already.
Step 3) Using 'Terminal', change directory to the /Packages folder:
2013 SP1 Example:
- cd /Volumes/m_ccompxe_2013_sp1.X.YYY/Packages
- cd /Volumes/m_fcompxe_2013_sp1.X.YYY/Packages
Step 4) Use 'sudo' to run the Intel installer 'i_install': ./i_install with the silent install options.
Usage: ./i_install [OPTIONS]
For Version 2013 SP1: usage: sudo ./i_install [-s or -h] [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -xd 'xcode folder' -l 'log file' -it '[1/2]' -sd '[yes/no]' -eula 'accept'
User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.
Usage: ./i_install [OPTIONS]
For Version 2013 SP1: usage: sudo ./i_install [-s or -h] [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -xd 'xcode folder' -l 'log file' -it '[1/2]' -sd '[yes/no]' -eula 'accept'
User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.
Required Options
- -s : to indicate execute in silent mode
- -l : [optional] to provide a install log file (this file will be created '/tmp' folder. Do not use any path information, just some simple name like 'install.log'.
- -f : -licfile Install silently using the license file provided on the command line. Include the full path to the .lic license file on your system. Typically these are stored in directory /Users/Shared/Library/Application Support/Intel/Licenses/<file>.lic
- Port@host Install silently using the server license available at host
- -sn, -sn Install silently using the serial number provided on the command line
- -eula 'accept' to confirm that you have read the End User Licensing Agreement and have accepted the license conditions. By using silent installation you must accept the EULA and by using the silent installation you have agreed to those terms.
More required Options for all compilers Version 11.1 and above
- -id <install_dir> 'install directory', default install folder is /opt/intel
- Silent install utility installs all the packages bundled in the meta package.
- To set the top level install folder for these packages one can use this option
- -xd : 'xcode folder' ( provide Xcode IDE folder for compiler to be integrated with) - /Applications/Xcode.app for example or /Developer/XCode
More required Options for all compilers Version 12.0 and above (Composer XE 2011, Composer XE 2013, Composer XE 2013 SP1)
12.0 and 12.1 versions:
12.0 and 12.1 versions:
- -it: install type; 1. commandline install 2. xcode integration 3. both, command line and xcode environment.
- User has option to install either command line alone and/or integrate with xcode IDEenviromen
- Default install type is 3
More required options for all compilers version 13.0, 13.1, and 14.0: Composer XE 2013 and 2013 SP1 versions:
- -it: install type; 1. Command line install 2. both, command line and Xcode environment.
- User has option to install either command line alone or integrate with Xcode IDE enviroment
- Default install type is 2
- -sd: indicates agreement to participate in Intel(R) Software Improvement Program, by default is 'no'
Silent Installation Guide for Intel Compilers for Mac OS* X Version 11.x
Here are the steps you need to follow to install the Intel Compilers for Mac OS X* version 11.0 and higher in silent mode.
Step 0) Login as an administrative user or root. If you have sudo priviledge, become root user in a Terminal window with:
- sudo bash
- and enter your user password, then enter command
- su -
Step 1) Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. OR If you are working from a terminal window, use the hdiutil command to mount the compiler installer disk image (.dmg)
11.0 Example (11.1 is similar):
Disk image mounts under
- /Volumes/m_cprof_p_11.0.0xx (for the 11.0 Fortran Compiler) or
- /Volumes/m_cproc_p_11.0.0xx (for the 11.0 C++ Compiler)
Mount image with
- hdiutil attach m_cprof_p_11.0.0xx.dmg
- hdiutil attach m_cproc_p_11.0.0xx.dmg
12.0 Example:
Disk image mounts under
- /Volumes/m_fcompxe_2011.u.vvv (for the 12.0 Fortran Compiler) or
- /Volumes/m_ccompxe_2011.u.vvv (for the 12.0 C++ Compiler)
Mount image with
- hdiutil attach m_fcompxe_2011.u.vvv.dmg
- hdiutil attach m_ccompxe_2011.u.vvv.dmg
where 'u' is the update number ( 0, 1, 2, 3, etc) and where 'vvv' is the specific version ( 2011.2.142 is Update 2, version 142 for example).
Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already. Do this as root user or use the command 'sudo bash' to become root user)
Step 3) Using 'Terminal' as root user, change directory to the /Plugins folder:
11.0 (similarly for 11.1):
Change directory to the 'Plugins' folder inside /Volumes/m_cprof_p_11.0.0xx
For example:
- cd /Volumes/m_cproc_p_11.0.0xx/m_cproc_p_11.0.0xx.mpkg/Contents/Plugins
- cd /Volumes/m_cprof_p_11.0.0xx/m_cproc_p_11.0.0xx.mpkg/Contents/Plugins
12.0:
- cd /Volumes/m_ccompxe_2011.2.142/m_ccompxe_2011.2.142.mpkg/Contents/Plugins
- cd /Volumes/m_fcompxe_2011.2.142/m_fcompxe_2011.2.142.mpkg/Contents/Plugins
Step 4) Run installer 'i_install': ./i_install with the silent install options.
Usage: ./i_install [OPTION]
For version 11.0: usage: ./i_install [-s or -h] -l 'log file' -f 'license file or folder or port@host' -eula 'accept'
For version 11.1: usage: ./i_install [-s or -h] -l 'log file' -f 'license file or folder or port@host' -sn 'serialnumber' -xd 'xcode folder' -id 'install folder' -eula 'accept'
Mac Os X Tiger For Intel
For Version 12.0: usage: ./i_install [-s or -h] -l 'log file' [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -it '[1/2/3]'-xd 'xcode folder' -id 'install folder' -eula 'accept'
![Intel Intel](/uploads/1/3/4/5/134519719/933101710.jpg)
User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.
Required Options
Mac Os X Intel Core 2 Duo
- -s : to indicate execute in silent mode
- -l : [optional] to provide a install log file (this file will be created '/tmp' folder
- -f : -licfile Install silently using the license file provided on the command line.
- Port@host Install silently using the server license available at host
- -sn, -sn Install silently using the serial number provided on the command line
Additional Options, Version 11.1 and above
- -id <install_dir> 'install directory', default install folder is /opt/intel
- Silent install utility installs all the packages bundled in the meta package.
- To set the top level install folder for these packages one can use this option
- If install_dir is provided then the mounted system has to be writable for silent installs
- If the mounted volume is not writable, then user gets'Seems mounted volume is read only file system. Use 'hdiutil attach '<disk-image-name>.dmg' -readwrite -shadow' command, to mount the disk image', message and aborts silent install.
- -xd : 'xcode folder' ( provide xcode IDE folder for compiler to be intgegared with)
Additional Options, Version 12.0 and above
- -it: install type; 1. commandline install 2. xcode integration 3. both, command line and xcode environment.
- User has option to install either command line alone and/or integrate with xcode IDEenviroment
- Default install type is 3
- -h Display the silent install usage.
Examples:
Log File
Option, '-l mylog_file' creates a install log file 'tmp/mylog_file', if this argument is not given then'/tmp/pset.log' file is created for logs.
Silent Installation Guide for Intel Compilers for Mac OS* X Version 10.1
Here are the steps you need to follow to install the Intel Compilers for Mac OS X* version 10.1 in silent mode.
- Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. If you are working from a terminal window, this command will mount the compiler installer disk image under /Volumes/m_fc_p_10.1.0xx (for the Fortran Compiler) or /Volumes/m_cc_p_10.1.0xx (for the C++ compiler)
- hdiutil attach m_fc_p_10.1.0xx.dmg
- hdiutil attach m_cc_p_10.1.0xx.dmg
- Start a 'Terminal' program from Utilities group (if you have not done so already). Using 'Terminal' do the following:
- Copy the contents of the mounted image to a local folder, for example:
- cp -pR /Volumes/m_fc_p_10.1.00x /Users/f_fc_p_10.1.00x (or the similar command for m_cc_p_10.1.0xx)
- Change directory to the local 'instman' folder inside the folder you copied in (a), for example:
- cd /Users/f_fc_p_10.1.00x/instman
- Export DYLD_LIBRARY_PATH=<instman folder>, for example:
- export DYLD_LIBRARY_PATH=/Users/f_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
- (optional) Make changes to ‘si_issa.xml' configuration file to change the default settings, see details below.
- Run: ./si_secore with the silent install options. Usage: /si_secore [OPTION]
The user must provide a valid serial number following the -sn option and a license file with the complete path following the --licfile option. -n, -sn Install silently using the serial number provided on the command line. The other settings will come from 'si_issa.xml' file in the instman folder or from a custom config file, specified as -c 'your config' on the command line.
- -l, -licfile Install silently using the license file provided on the command line. The other settings will come from 'si_issa.xml' file present in the instman folder or from the -c 'your config' file provided on the command line.
- -c Use ISSA and install parameters that are supplied through this configuration file.
- -h Display the silent install usage.
Precedence Order for Parameters
- If both -sn 'SN' and the -c 'CF' options are provided, the serial number provided via command line overrides the serial number specified in the <SerialNumber> value in the configuration file.
- If both -licfile 'LF' and the -c 'CF' options are provided, the license file provided via command line overrides the license file specified in the <LicenseFile> value in the configuration file.
- If both <SerialNumber> and <LicenseFile> values are provided in the configuration file or as command-line options, silent install will first copy the license file, validate and proceed with the install; if install fails, it will follow the serial number option path.
Configuration File
The default configuration file 'si_issa.xml' is available in the ‘instman' folder. You can use the script file 'pre_sinstall.sh' available in the 'instman' folder to generate an silent install config file. Here is an example of the format of this configuration file
Note: the pkg_id attribute under <Package pkg_id='1'> will set the order in which the tools will be installed. You can change the install order based on dependencies between installed packages. Include the <Proxy> section only if a web proxy server is required to reach the Intel® Software Development Products Registration Center web server.
Examples:
Log File
To create a log file, create a directory named 'WorkArea' within the 'instman' folder. Rerun the installation, and files will be created in the 'WorkArea' folder. The most important file will be secore.log, which is a transcript of the ISSA session.
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 user's 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
To create a log file, create a directory named 'WorkArea' within the 'instman' folder. Rerun the installation, and files will be created in the 'WorkArea' folder. The most important file will be secore.log, which is a transcript of the ISSA session.
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 user's 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
- Mount the product dmg file with required content using Finder, for example, by double-clicking on the dmg file.
- Start a Terminal program from the Utilities group. Using Terminal, 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
- 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
- Start a shell session under bash, for example:
- sudo /bin/bash
- Export DYLD_LIBRARY_PATH=<instman folder>, for example:
- export DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
- (optional) Make changes to si_issa.xml configuration file to change the default settings, see details below.
- Run ./si_sicore with options as described above.
Mac Os X For Intel Pc
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.
The following method uses sudo in a mode suitable for scripted automation.
- Start a Terminal program from the Utilities, or create a user shell (rsh, X11, etc)
- Change directories to a working area where the user has write permission. For example, cd /Users/<my user> ,where this is the home directory of user <my user>. This example assumes the user has downloaded or copied the compiler disk image (.dmg) file to this user home directory /Users/<my user>/m_fc_p_10.1.0xx.dmg where '0xx' is the compiler minor version.
- 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 hdiutil attach m_fc_p_10.1.0xx.dmg
- 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/<my user> , where '<my user>' is replaced by your login or user name.
- Change directories to /Users/<my users>/m_fc_p_10.1.0xx/instman created by the previous copy command: cd /Users/<my user>/m_fc_p_10.1.0xx/instman
- Use sudo to run the installer, using one of two possible methods, where '<options>' are replaced by si_secore options described above.
- sudo env DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ./si_secore <options>
- sudo -c 'DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ; ./si_secore <options> '
- For example, to use the serial number XXXX-XXXXXX to install:
- sudo -c 'DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ; ./si_secore -n XXXX-XXXXXX '
- (optional) Remove the compiler installation files. For example,
- cd /Users/<my user>
- rm -Rf m_fc_p_10.1.0xx
- (optional) Unmount the compiler installation image. For example, sudo hdiutil 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 <options> <command> , where ‘MyPassword' is your user password used to run sudo command.
Note
As noted in the Intel® Software Development Product End User License Agreement, the Intel® Software Development Product you install will send Intel the product’s serial number and other system information to help Intel improve the product and validate license compliance. No personal information will be transmitted.
Jump to: navigation, search
QEMU is a Virtual Machine system a bit like VirtualBox or VMware except if VT-X is not supported by your CPU, there is a good chance QEMU can still run OS X!It may be theoretically possible to have a download and boot script that runs OS X on a broad array of x86_64 computers.But for now that's another story.
You may also find the lengthy descriptions for Vmware interesting.
[edit]Progress table for running on OS X entirely in software
Below is messy, I thought a table might be a good idea perhaps with fields like:OS X VersionBoot Image / file source commentsOS X Image / file sourceWhat works:Network?Automatic Updates?Soundcard?Install Arguments (e.g: cdrom iso filename)Post-install Arguments (network etc)Notes
Please allow the table to become as simple and instructional as possible.
OS X Version | Boot Image / file source comments | OS X Image / file source | What works: | Network? | Automatic Updates? | Automatic Updates? | Soundcard? | QEMU Install Arguments (e.g: cdrom iso filename) | Post-install Arguments (network etc) | Notes |
---|
[edit]qemu 0.7
(Taken from Emulation Progress)
Here may be (?) a sample command to use (on Windows, and on others just loose the '.exe'):
And at the bootloader, you have to pass those option:
[edit]qemu 0.9
(Taken from Emulation Progress)
Using a deadmoo image(10.4.1) (qemu for windows 0.9.0), boot is successful with boot parameters
(other graphics modes may be used). Jas install images do not work as yet.
[edit]qemu 0.9.1
qemu boots and installs properly with something like this:
First, hit F12 to tell the qemu BIOS to boot off the CD. Immediately thereafter, hit F8 in the Darwin loader. You can type '-v', but don't have to. Then continue ... and don't move the mouse too hastily.
Unfortunately, the resulting hard disk won't be recognized by qemu's BIOS - you don't even get to the F8 prompt. Besides this, it's slow. Installation takes 2 hours on a Core2Duo 2.2 GHz. Both, the '-smp 2' and the '-kernel-kqemu' options passed to qemu result in Leopard boot failures.
QEMU running 10.4.8 Tiger
Qemu can also run an installation of 10.4.8 made with VMware:
[edit]qemu 0.10.0
Mac Os X For Intel Pentium
qemu 0.10.0 can do everything 0.9.1 could do. Additionally, it fixes enough bugs to be useable. Leopard installs and runs, with all the quirks you see on real hardware, though. Leopard (and likely Tiger) requires the -legacy option at the F8 prompt or in com.apple.boot.plist.
- Graphics: 'std' is fine, 'cirrus' ist almost good and 'vmware' doesn't get beyond the text console.
- Ethernet: Of the many available NICs, the RTL8139 appears to be the only one visible to the network control panel. Downloads are shaky, but improve a lot if you run a 'ping google.com' (or some other host) at the same time.
- Audio: Not tested.
- Misc: Make sure the machine doesn't go to sleep, there's no mechanism to wake it.
[edit]qemu 0.14.1
I had my host system running Debian Linux testing with Linux kernel 2.6.39.1 and qemu-kvm 0.14.1. I had latest Intel xorg video driver installed on my host for my new i5 2400. I tried 10.6.6i snow leopard by Hazard on my qemu which is very good without any lag and network/audio are both enabled.
My host system is
- Intel i5 2400 with embedded HD 2000 video
- Gigabyte H61M D2P B3
- Crucial Ballistix 8G DDR3 1333
- Hitachi 1T 7k1000c with AHCI enabled.
The qemu parameters:
- Graphics: 'std' is fine, I add one more -sdl to the parameter of qemu but I don't know if there is any difference.
- Ethernet: with the default AppleRTL8139Ethernet.kext at /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns. I use the bridge mode of qemu so my OSX86 looks like one of host in my local network, which gets the DHCP from my wireless router. I think the general user mode of qemu should be workable too. The important qemu parameters for the network is -net nic,model=rtl8139 -no-kvm-irqchip. If you don't use bridge mode, you should add -net user too. The -no-kvm-irqchip is a tricky parameter too and it won't worked if no such parameter.
- Audio: use parameter '-soundhw all' in qemu-kvm the you get the noisy youtube.
My final qemu invocation command is
where tap device is created by tunctl and be added into bridge with brctl
There are 2 tricks to run the 10.6.6i with RTL8130 up on qemu,
1. When booting the iso and doing first installation, kernel will panic at ElliotForceLegacyRTC so I have to delete the kext in both CD and new-installed volume hence do the following:
2. When booting the kernel in hard drive, give the '-v -f -F' in the bootloader.
Retrieved from 'http://wiki.osx86project.org/wiki/index.php?title=Qemu&oldid=63575'
This page was last modified on 22 May 2012, at 02:18.
This page has been accessed 54,668 times.