CST STUDIO SUITE® 2014Installation Guide - Linux Version

Contents1 Introduction 3

1.1 Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Supported Linux Distributions . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Installation 52.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Installation with Graphical Installer . . . . . . . . . . . . . . . . . . . . . . 62.3 Command Line Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 Silent Mode Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.5 Installation on a Central Server . . . . . . . . . . . . . . . . . . . . . . . . 17

3 Usage Guideline for the Command Line Interface 183.1 Updating Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2 Starting CST Simulations from the Command Line . . . . . . . . . . . . . 183.3 Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.4 Limitations of the Command Line Interface . . . . . . . . . . . . . . . . . 223.5 Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 CST BOARDCHECK Graphical User Interface 234.1 Starting the CST BOARDCHECK Graphical User Interface . . . . . . . . 234.2 Updating Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.3 Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Troubleshooting 245.1 Installer reports ”Previous version found in NULL” . . . . . . . . . . . . . 245.2 Installer Shows Java Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 245.3 Installation from DVD Fails . . . . . . . . . . . . . . . . . . . . . . . . . . 245.4 Failed to Load Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . 245.5 Update of the Installation Fails . . . . . . . . . . . . . . . . . . . . . . . . 245.6 Installation of Prerequisite Packages Fails . . . . . . . . . . . . . . . . . . 255.7 Complete List of Required Packages . . . . . . . . . . . . . . . . . . . . . 25

A Technical Information 27

B Installation on Unsupported Distributions 28B.1 Debian 6 (64-bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29B.2 Ubuntu 12.04 (64-bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

February 11, 2014 2

(a) (b) (c)

Figure 1: (a) The CST software on the Linux computers is controlled by a CST STUDIOSUITE® frontend running on Windows using Distributed Computing or MPI computing. (b)The CST simulations on the Linux system are started in batch mode directly on the Linuxsystem. (c) The stand-alone application CST BOARDCHECK™ is started locally.

1 IntroductionThis document contains important information about the installation and usage of CSTSTUDIO SUITE® on Linux systems. Please read this manual carefully before installingthe software. If you need further help installing and configuring the software pleasecontact the CST support team (info@cst.com). We will be glad to help you.

1.1 Application ScenariosThere are three application scenarios for the software this DVD contains:

1. You plan to use the CST Distributed Computing system or MPI Computing ona Linux cluster and drive these Linux machines with the CST STUDIO SUITE®

frontend from a computer running the Microsoft Windows® operating system (seefig. 1(a)). In this case it is sufficient to read section 2 of the document.

2. You plan to build up a pure Linux environment/cluster system where you start CSTsimulations from the command line in batch mode without involving any machinerunning the Microsoft Windows® operating system (see fig. 1(b)). Systems which re-quire this setup are typically Linux cluster systems which are isolated by a gatewaymachine from the rest of your LAN and which are controlled by queuing systems(e.g. LSF, OGE, Torque, PBS, HTCondor). This setup can make use of the CSTDistributed Computing system and MPI Computing as well. The difference as op-posed to 1 is that there is no CST STUDIO SUITE® frontend running on MicrosoftWindows® involved during the simulation run1.

3. You plan to deploy the application CST BOARDCHECK™ on a single machine. Inthis configuration both the computations and the GUI visualization can be run on aLinux machine (fig. 1(c)). See section 4 for details.

1Although you don’t need to have a machine running Microsoft Windows® in your cluster you will stillneed an installation of CST STUDIO SUITE® on a computer running Microsoft Windows® to create yourmodels.

February 11, 2014 3

1.2 Supported Linux DistributionsThis version of CST STUDIO SUITE® is supported and continously tested on RedHatEnterprise Linux 5.x and 6.x as well as SUSE Linux Enterprise Server (SLES) 11. It maywork on other distributions as well, but we strongly recommend using it on one of thesupported configurations and won’t be able to support you if you experience problemswith a Linux version not listed here. Nevertheless, you can find some information aboutthe installation on some distributions which are not officially supported in appendix B.Part of this information was kindly provided by some of our customers.

1.3 NomenclatureThe following section explains the nomenclature used in this document.

$ command Commands you have to enter on a command prompt as a normaluser (not root) are typeset using typewriter fonts and highlightedwith a gray box. The ”$” sign in front of the command symbolizesyour command prompt and must not be entered.

# command Commands you have to enter on a command prompt as user rootare typeset in red color. The ”#” sign in front of the commandsymbolizes the root command prompt and must not be entered.

<...> Within commands the sections you should replace according to yourenvironment are enclosed in ”<...>”. For example ”<CST_DIR>”should be replaced by the directory where you have installed CSTSTUDIO SUITE® (e.g. ”/opt/cst/CST_STUDIO_SUITE_2014”).

February 11, 2014 4

2 Installation2.1 PrerequisitesPlease make sure that your environment is configured in the following way before youstart the installation.

1. Some Linux distributions will automatically mount the installation DVD but withthe noexec mount option which prevents the execution of the installer. Please mountthe DVD manually or use the command# mount -o remount,exec /media/CST_STUDIO_SUITE_2014_Linux

to circumvent this issue.

2. Change /etc/hosts according to http://dev.mainsoft.com/Default.aspx?tabid=103.Afterwards /etc/hosts should contain a

127.0.0.1 localhost.localdomain localhost

line and no further 127.0.0.1 lines. Additionally, if you plan to use MPI Comput-ing, make sure that the names of your nodes can be resolved to IPv4 addresses (notto IPv6 addresses). You can use the command$ ping <hostname>

to test whether <hostname> can be resolved properly.

3. If you want to install a part of CST STUDIO SUITE® which needs a service runningon your system (needed for Distributed Computing or license server) you must runthe installer with root permissions. In case of security concerns please contact CSTsupport (info@cst.com) for advice or read FAQ 373 (Distributed Computing) or FAQ286 (license server) on the CST support webpage.Superuser permissions are however not needed for the services to run: you can specifya user account for that purpose. Note that this user account must exist before youstart the installation.

4. If you plan to use MPI Computing: Please note that MPI Computing needs a DNSor appropriate entries in the /etc/hosts file in order to start up remote processeson compute nodes. Please refer to the online help for further information on how tosetup a Linux cluster with MPI.

5. CST STUDIO SUITE® requires that several software libraries are preinstalled on thetarget system. The installer checks only its own list of libs required to successfullyexecute the installer but not the CST software itself.After the installation has finished it is strongly recommended to execute the tool$ "<CST_INSTALL_PATH>/cst_system_check"

February 11, 2014 5

which can test whether all libraries and tools required to use the CST software arepresent on your system.Additionally you can find the full list of required packages for the supported distri-butions in section 5.7.

2.2 Installation with Graphical InstallerAfter mounting the DVD into your file system go to the root directory of the DVD andexecute the installer by using the command# ./install.shNote: If the machine you are installing on provides a desktop environment (a running X-server), the installer will be executed in the so-called GUI mode. If it does not provide adesktop environment please continue reading with section ”Command Line Installation”(section 2.3). The console mode can also be selected manually by starting# ./install.sh --nogui

1. After you have started the installer you should see the following window. Just clickon ”Next” to proceed.

February 11, 2014 6

2. Please read the license agreement carefully. If you agree with the license terms selectthe option ”I accept the terms of the License Agreement” and press ”Next”.

3. Please choose your installation set by selecting/unselecting the checkboxes. Thenpress ”Next” to proceed.Note: The component ”Command line interface and CST BOARDCHECK” is onlyneeded if you want to start simulations in batch mode either from a terminal or viaa queueing system or if you want to use CST BOARDCHECK™. Please do NOTinstall this component if you set up a CST Distributed Computing systemor an MPI cluster to which users send their jobs directly from the CSTSTUDIO SUITE® Windows frontend.

February 11, 2014 7

4. If you selected an installer feature that needs to run a service on your system (e.g. theDistributed Computing components or the license server) and the installation wasn’tstarted with root permissions you’ll get the following warning. Either leave theinstaller and restart with superuser permissions or change the selection of features.

5. You will see the following warning if you’ve selected one of the Distributed Comput-ing components (DC Main Controller, DC Solver Server) as well as the ”Commandline interface and CST BOARDCHECK” component in the previous step. As theDC update mechanism is currently not aware of any files needed by the ”Commandline interface and CST BOARDCHECK” you will need to update every installa-tion containing this component using the update packages you get from CST (seesection 3.1).

February 11, 2014 8

6. If you have selected the ”Command line interface and CST BOARDCHECK” optionyou will be asked if you want to install a license file on the local machine.Note: The license file should be installed only on the machine which is equippedwith the hardware (MAC or dongle) for which the license file was issued.

7. If you chose to install the local license server you will be asked for a license file.Please specify the full path to the license file.

February 11, 2014 9

8. If you decided not to install a local license server you will need to specify the name ofthe remote license server and the port on which the license server is listening in theformat <port_number>@<computer_name>. The port_number setting is optional.

9. If you selected the DC Solver Server for installation you will be asked to which DCMain Controller this Solver Server should connect to.

February 11, 2014 10

10. Next you will be asked for the so-called ”Main User”. This is the user account underwhich the CST daemons will be started. Additionally, only this user account (androot) has the permission to configure the CST daemons and to update the installationwith service packs. The ”Main User” needs to be a user account already existing onthe system.

11. Choose the installation folder. Please do not use spaces within this path.

February 11, 2014 11

12. Check all the settings you made and start the installation.

2.3 Command Line InstallationIf no running X server is found, the installer will automatically switch into a console mode.You can however override the detection logic by running# ./install.sh --nogui

1. When you see the first page of the text based installer, just press enter to continue.Note: On any page of the installer you may go to the previous page by entering”back”.

2. Please read the license agreement carefully. If you agree with the license terms enter”Y” and press ”enter” to proceed.

February 11, 2014 12

3. Choose your install set by entering the number of the features you would like toinstall as a comma separated list and press ”enter” to proceed. Please note thatentering the number of a feature which is already selected will deselectthis feature. On the picture below, feature number 1 is already selected. If youwrite ”1” again in the comma separated list, it will be deselected.Note: The component ”Command line interface and CST BOARDCHECK” is onlyneeded if you want to start simulations in batch mode either from a terminal or viaa queueing system or if you want to use CST BOARDCHECK™. Please do NOTinstall this component if you set up a CST Distributed Computing systemor an MPI cluster to which users send their jobs directly from the CSTSTUDIO SUITE® Windows frontend.

4. If you selected an installer feature that needs to run a service on your system (e.g.Distributed Computing or the license server) and the installation wasn’t startedwith root permissions you’ll get the following warning. Either leave the installer andrestart with superuser permissions or change the selection of features.

February 11, 2014 13

5. You will see the following warning if you’ve selected one of the Distributed Comput-ing components (DC Main Controller, DC Solver Server) as well as the ”Commandline interface and CST BOARDCHECK” component in the previous step. As theDC update mechanism is currently not aware of any files needed by the ”Commandline interface and CST BOARDCHECK” you will need to update every installa-tion containing this component using the update packages you get from CST (seesection 3.1).

6. You will be asked if you want to provide a license file (the file must be issued for thelocal machine) or if you want to connect to a remote license server.

7. If you chose to install the local license server you will be asked for a license file.Please specify the full path to the license file.

February 11, 2014 14

8. If you decided not to install a local license server then you need to specify the nameof the remote license server and the port on which the license server is listening in theformat <port_number>@<computer_name>. The port_number setting is optional.

9. If you selected the DC Solver Server for installation you will be asked to which DCMain Controller this Solver Server should connect to.

10. Next you will be asked for the so-called ”Main User”. This is the user account underwhich the CST daemons will be started. Additionally, only this user account (androot) has the permission to configure the CST daemons and update the installationwith service packs. The ”Main User” needs to be a user account already existing onthe system.

11. Choose the installation folder. Please do not use spaces within this path.

February 11, 2014 15

12. Check all the settings you made and start the installation.

February 11, 2014 16

2.4 Silent Mode InstallationIt is possible to generate an installer configuration file which enables silent mode installa-tion. This is useful if you want to deploy the software to several machines using the sameinstaller settings. To generate such a file, start the installer with the option --record:# ./install.sh --record <filename>The installer will store a file with all settings you made during the installation process.This file can be used for later installations:# ./install.sh --replay <filename>

The installer will now read all required settings from the configuration file and perform anunattended installation.

2.5 Installation on a Central ServerIt is possible to install the CST STUDIO SUITE® on a central server, mount the instal-lation directory on a client machine, and use the software on the client machine. If youchoose this type of installation be aware that the installation directory on the server musthave the same name as the mountpoint on the client machine, i.e. if you installed the soft-ware on the fileserver using /opt/cst/CST_STUDIO_SUITE as installation path then thefolder must be mounted into the filesystem of the client such that it occurs with the samename (/opt/cst/CST_STUDIO_SUITE) on the client. Additionally, be aware that the CSTdaemons can’t be automatically installed on the client machine. This fact leads to thefollowing limitations:

2.5.1 Limitations

The Distributed Computing system cannot be set up automatically using a central instal-lation as described above. It is however possible to start the system manually. Please referto FAQ 373 in the support section of the CST website.

February 11, 2014 17

3 Usage Guideline for the Command Line InterfaceThis section contains information about the setup and use of the CST command line inter-face which enables you to start simulations in batch mode from a terminal or via a queuingsystem. If you haven’t installed the ”Command line interface and CST BOARDCHECK”component you can skip this section.

3.1 Updating Your InstallationTo update your installation of CST STUDIO SUITE® use the command$ "<CST_INSTALL_DIR>/update_with_supfile" "<FULL_PATH_TO_SUPFILE>"

This command can be executed by the ”Main User” you have defined during the installa-tion process or by root (see installation step 10 in section 2.2 or 2.3, respectively). Replacethe terms <CST_INSTALL_DIR> and <FULL_PATH_TO_SUPFILE> with the directory whereyou have installed CST STUDIO SUITE® and with the full path of the patch file youdownloaded from the support section of the CST website, respectively. The quotes aremandatory. The files used to update the Windows version of CST STUDIO SUITE® can-not be used to update the Linux ”Command line interface”.The service packs for this software can be downloaded from within the support area of theCST webpage.

3.2 Starting CST Simulations from the Command LinePrior to starting any CST simulations please run the cst_system_check script at leastonce. The script will report missing packages and programs that are required to run aCST simulation.$ "<CST_INSTALL_PATH>/cst_system_check"

To start your simulations please use the following syntax:$ "<CST_INSTALL_PATH>/cst_design_environment" <OPTIONS> "<PATH_TO_CST_FILE>"

The quotes are recommended to prevent problems with special characters in the path. Notethat at least two command line switches need to be specified: one to select the module (e.g.--m for MICROWAVE STUDIO), and one to select the solver (e.g. --r for the transientsolver).The CST command line interface currently supports the following command line options:

Option Behavior

--m Starts CST MICROWAVE STUDIO®

--t Starts CST PARTICLE STUDIO®

February 11, 2014 18

--r Starts the transient solver (T-Solver).

--f Starts the frequency domain solver (F-Solver).

--q Starts the integral equation solver (I-Solver).

--a Starts the asymptotic solver (A-Solver).

--pic Starts the particle in cell solver (PIC-Solver).

--tp Starts the particle tracking solver (Trk-Solver).

--tw Starts the wakefield solver (WAK-Solver).

--p Starts a parameter sweep. This option always uses thesolver that was used last for the saved project.

--o Starts the optimizer. This option always uses the solverthat was used last for the saved project.

--withgpu="<N>"

Starts the solver on GPU hardware. N specifies the numberof GPUs which should be used for the simulation. Thisoption is only available for the transient solver (option --r),PIC solver (--pic) or integral equation solver (--q). Pleaserefer to the GPU Computing Guide to learn more aboutGPU Computing.

--withmpi

Enables MPI computing. Also a machinefile must be spec-ified when using MPI Computing. Valid for --r, --f, --qand --tw.Please refer to the online help to learn more about MPIComputing.

--withdc--withdc="<MAINCTRL>"

Starts the specified solver with Distributed Computing. Ifno main controller is specified, the main controller from theglobal or project dependent settings are taken. Otherwisethe specified main controller is used.

--dc <N>This option sets the distributed excitations or frequencysamples to N. Only valid for --withdc and --r and --f.Example: --dc 6

--dcpar <N>Sets the number of distributed parameter sets to N. Onlyvalid for --withdc and --p and --o.

February 11, 2014 19

--machinefile "<MFILE>"

Defines the location of the machine file path MFILE, in orderto use MPI simulation jointly with a given queuing systemlauncher. Must be used with --withmpi and can be usedwith --withdc

--queuesys "<QS>"

Defines the queueing system. Currently available queueingsystem tags for QS are: CST, MPI, SGE, OGE, PBS, LSF andLSF_MCPU.Can be used with --withmpi and with --withdc

--numthreads <N>Defines the number of threads to be used for the givensimulation. Default is to use all CPU cores.

--defaultacc

Overwrites all project specific acceleration settings (relatedto threads, DC, MPI and GPU computing) to their defaultsettings. All command line options related to accelerationare taken still into account, though.

--dump <N>Update results every N minute(s) when a solver is running.Only valid for --m or --t.

February 11, 2014 20

3.3 Environment VariablesThe CST ”Command line interface” currently supports the following environment variables.

• CST_VERBOSE_FRONTEND – If set to ”0” the output of the solvers will be suppressed.By default the output is shown on the console.

• CST_WAIT_FOR_LICENSE – If set to ”1” the program will wait in case that the licenserequired to start your simulation is blocked by another simulation. The simulationwill start as soon as the license is free again. If the environment variable is not setthe program will end immediately in case that the required license is already in use.

• CST_LOCALHOME – By default, crucial runtime files (i.e. shared memory segments)which are required to run CST STUDIO SUITE® are created in the /tmp folder.The CST_LOCALHOME variable allows the user to change the location where thesefiles are stored. Note: The path specified must exist and it must point to a localstorage device (not to a folder located on a file-server). All user accounts using CSTSTUDIO SUITE® need to have write-access to this folder. We recommend to not setthis variable unless /tmp does not reside on a local storage device.In case of a stateless cluster, where all drives are mounted shared drives, the RAM-disk might be used:$ export CST_LOCALHOME=/dev/shm

• CST_ENABLE_INTERACTIVE_RESULT_VIEW – By setting this environment variable to”1” CST STUDIO SUITE® can be started interactively, provided the DISPLAY vari-able points to a visible X display. CST STUDIO SUITE® may then be invoked likethis:$ "<CST_INSTALL_PATH>/cst_design_environment" "<PATH_TO_CST_FILE>"

Be aware that the <PATH_TO_CST_FILE> file must not be in use by another instanceof CST STUDIO SUITE®.Note: The interactive mode of CST STUDIO SUITE® is currently meant for resultviewing only although other parts of the software (e.g. modeling) are enabled as well.These other parts are currently not considered stable enough for production use.

• CST_FORCE_SOFTWARE_RENDERER – CST STUDIO SUITE® uses GPU accelerated3D rendering by default when started interactively, i.e. if the environment variableCST_ENABLE_INTERACTIVE_RESULT_VIEW is set. However, some GPU drivers areunable to handle OpenGL commands properly. If you experience issues with 3Drendering on your system you may switch off GPU accelerated rendering by settingCST_FORCE_SOFTWARE_RENDERER to 1.

February 11, 2014 21

3.4 Limitations of the Command Line InterfaceThis version of the ”Command line interface” only supports the following solvers/features.This is subject to change and we expect this table to grow significantly for future releases:

Supported Solver Known Limitations

Transient TLM solver on Linux can’t be started using the Com-mand Line Interface.2

Frequency Domain Inhomogeneously Biased Ferrites are currently un-supported

Integral Equation None

Asymptotic None

PIC None

Tracking None

Wakefield None

If you have an urgent need for some of the other solvers please let us know. We can takethis into account when planning the further process of porting the software and you mayeven help us to make it more robust on the Linux platform as a beta tester if you like.

3.5 UninstallGo into the "<CST_INSTALL_DIR>/Uninstall CST_STUDIO_SUITE_2014" directory andrun the command# ./Uninstall\ CST_STUDIO_SUITE_2014

to uninstall the software.

2The TLM solver can be used on Linux via Distributed Computing when started by the CST frontendrunning on Windows.

February 11, 2014 22

4 CST BOARDCHECK Graphical User InterfaceThis section contains information about the setup and use of CST BOARDCHECK™which enables you to start a PCB analysis from a graphical user interface. If you haven’tinstalled the ”Command line interface and CST BOARDCHECK” component you can skipthis section.

4.1 Starting the CST BOARDCHECK Graphical User InterfaceTo start CST BOARDCHECK™ please use the following syntax:$ "<CST_INSTALL_PATH>/cst_boardcheck"

The quotes are recommended to prevent problems with special characters in the path.This command opens a graphical user interface where CST BOARDCHECK™ can bestarted and used just like the Microsoft Windows® version.

4.2 Updating Your InstallationTo update your installation of CST STUDIO SUITE® use the command$ "<CST_INSTALL_DIR>/update_with_supfile" "<FULL_PATH_TO_SUPFILE>"

This command can be executed by the ”Main User” you have defined during the installa-tion process or by root (see installation step 10 in section 2.2 or 2.3, respectively). Replacethe terms <CST_INSTALL_DIR> and <FULL_PATH_TO_SUPFILE> with the directory whereyou have installed CST STUDIO SUITE® and with the full path of the patch file youdownloaded from the support section of the CST website, respectively. The quotes aremandatory. The files used to update the Windows version of CST STUDIO SUITE® can-not be used to update the Linux ”Command line interface and CST BOARDCHECK”.The service packs for this software can be downloaded from within the support area of theCST webpage.

4.3 UninstallGo into the "<CST_INSTALL_DIR>/Uninstall CST_STUDIO_SUITE_2014" directory andrun the command# ./Uninstall\ CST_STUDIO_SUITE_2014

to uninstall the software.

February 11, 2014 23

5 Troubleshooting5.1 Installer reports ”Previous version found in NULL”If the installer shows the error message Previous version found, this likely means thatthe CST installation folder has been deleted without running the uninstall program. Theinstaller ”remembers” a previous installation using a hidden file. If you delete this file with# rm /var/.com.zerog.registry.xml

you can reinstall the software. However, please use the uninstall program (located in"<CST_INSTALL_DIR>/Uninstall CST_STUDIO_SUITE_2014") if you want to remove thesoftware from your system as it reverts all changes applied during installation and alsoremoves this hidden file.

5.2 Installer Shows Java ErrorsIf the installer fails with a Java error this is most likely due to an incompatible Javaversion on your system. However, the installer has its own Java version and you can forcethe installer to use this built-in version using the option --installerjava.

5.3 Installation from DVD FailsTypically, the automount of the RedHat Enterprise system will mount the DVD with thenoexec flag which prevents starting programs from a DVD. Thus, if the installer fails tostart from the DVD you might have mounted the DVD with incorrect options. In thiscase please unmount the DVD using the umount command and mount it again using thefollowing command:# mount -t iso9660 -o loop,ro,exec,map=off /dev/cdrom /media/cdrom

Please create the directory /media/cdrom if it does not exist.

5.4 Failed to Load Shared LibraryThe CST software package has as few dependencies as possible on external libraries. How-ever, in some rare cases you may get an error about a missing library.If you experience trouble please run the$ "<CST_INSTALL_PATH>/cst_system_check"

to detect and optionally install missing dependencies.

5.5 Update of the Installation FailsIf the update of your installation fails please check the following points:

• The update can be performed by the ”Main User” (defined during the installationprocess) or by root. It will fail for any other user account.

February 11, 2014 24

• Currently the patch files for the Microsoft Windows® version of CST STUDIO SUITE®

are incompatible with the Linux version. Please ensure that you used the correctpatch file.

5.6 Installation of Prerequisite Packages FailsIf the installation of prerequisite packages with$ yum install ...

fails with errors like

Error: Protected multilib versions: ...You could try using --skip-broken to work around the problemYou could try running: rpm -Va --nofiles --nodigest

please try to first update your system to the latest version with the command$ yum update

5.7 Complete List of Required Packages5.7.1 RHEL 6.x (64-bit)

util-linux-ng xorg-x11-server-Xvfb expat.i686 fontconfig.i686freetype.i686 glibc.i686 libICE.i686 libSM.i686 libX11.i686libXau.i686 libXdamage.i686 libXext.i686 libXfixes.i686libXrender.i686 libXxf86vm.i686 libXt.i686 libdrm.i686 libgcc.i686libpng.i686 libstdc++.i686 libuuid.i686 libxcb.i686 mesa-libGL.i686mesa-libGLU.i686 zlib.i686 expat.x86_64 fontconfig.x86_64freetype.x86_64 glibc.x86_64 libICE.x86_64 libSM.x86_64libX11.x86_64 libXau.x86_64 libXdamage.x86_64 libXext.x86_64libXfixes.x86_64 libXft.x86_64 libXfont.x86_64 libXi.x86_64libXmu.x86_64 libXp.x86_64 libXpm.x86_64 libXrender.x86_64libXt.x86_64 libXxf86vm.x86_64 libdrm.x86_64 libgcc.x86_64libjpeg.x86_64 libpng.x86_64 libstdc++.x86_64 libuuid.x86_64libxcb.x86_64 mesa-libGL.x86_64 mesa-libGLU.x86_64mesa-libGLw.x86_64 openmotif.x86_64 zlib.x86_64 python-libs

5.7.2 RHEL 5.x (64-bit)

setarch xorg-x11-server-Xvfb expat.i386 fontconfig.i386freetype.i386 glibc.i386 libICE.i386 libSM.i386 libX11.i386libXau.i386 libXdmcp.i386 libXext.i386 libXrender.i386 libXt.i386libgcc.i386 libpng.i386 libstdc++.i386 mesa-libGL.i386 zlib.i386mesa-libGLU.i386 zlib.x86_64 expat.x86_64 fontconfig.x86_64freetype.x86_64 glibc.x86_64 libICE.x86_64 libSM.x86_64

February 11, 2014 25

libX11.x86_64 libXau.x86_64 libXfont.x86_64 libXdmcp.x86_64libXext.x86_64 libXi.x86_64 libXpm.x86_64 libXrender.x86_64libXt.x86_64 libgcc.x86_64 libjpeg.x86_64 libpng.x86_64libstdc++.x86_64 mesa-libGL.x86_64 mesa-libGLU.x86_64mesa-libGLw.x86_64 python-libs

5.7.3 SLES 11 (64-bit)

coreutils util-linux xorg-x11-server-extra Mesa-32bit fontconfigfreetype2-32bit glibc-32bit libdrm-32bit libexpat1-32bitlibgcc46-32bit libpng12-0-32bit libstdc++46-32bit libuuid1-32bitxorg-x11-libICE-32bit xorg-x11-libSM-32bit xorg-x11-libX11-32bitxorg-x11-libXau-32bit xorg-x11-libXext-32bitxorg-x11-libXfixes-32bit xorg-x11-libXrender-32bitxorg-x11-libXt-32bit xorg-x11-libs-32bit xorg-x11-libxcb-32bitzlib-32bit Mesa MesaGLw fontconfig freetype2 glibc libdrm libexpat1libgcc46 libjpeg libpng12-0 libstdc++46 libuuid1 openmotif-libsxorg-x11-libICE xorg-x11-libSM xorg-x11-libX11 xorg-x11-libXauxorg-x11-libXext xorg-x11-libXfixes xorg-x11-libXmu xorg-x11-libXpxorg-x11-libXpm xorg-x11-libXrender xorg-x11-libXt xorg-x11-libsxorg-x11-libxcb zlib

February 11, 2014 26

A Technical InformationThe CST Linux installer needs to install several files into system directories, e.g. to auto-matically start CST daemons with every system boot. Note that the uninstaller will undoall those changes.Depending on the choice of features different files have to be written. In the following textthe feature dependent steps will be marked as follows:

[MC] = CST DC Main Controller[SS] = CST DC Solver Server[FE] = Command Line Interface and CST BOARDCHECK™[LS] = License Server

1. The installation directory selected by the user will be created if it does not exist.None of the installed programs and libraries will get a setuid flag.

2. The following scripts will be installed in /etc/init.d:

- [SS] lsb-cst-solverserver2014- [MC] lsb-cst-maincontroller2014- [LS] lsb-cst-flexlm2014

and symlinks into the /etc/rcN.d directories for N = 3,4,5 will be created accordingto the usual Linux startup procedure depending on the features selected for instal-lation. Note that you can switch the services on and off with the Red Hat servicetool.

3. For menu entries and icons the following files will be written:

- XDGDATA/applications/cst/*.desktop- XDGDATA/desktop-directories/cst-studiosuite2014.directory- XDGDATA/pixmaps/cst-*.png- XDGDATA/icons/hicolor/16x16/apps/cst-*.png- XDGDATA/icons/hicolor/24x24/apps/cst-*.png- XDGDATA/icons/hicolor/32x32/apps/cst-*.png- XDGDATA/icons/hicolor/48x48/apps/cst-*.png- XDGDATA/icons/hicolor/scalable/apps/cst-*.png- XDGCONFIG/menus/applications-merged/cst-studiosuite2014.menu

where XDGDATA and XDGCONFIG depending on whether the superuser or a normal userperformed the installation:

February 11, 2014 27

Name root install user installXDGDATA /usr/share ˜/.local/shareXDGCONFIG /etc/xdg ˜/.config

This is according to the

• ”Desktop Entry Specification” and the• ”Desktop Menu Specification”

4. If [FE] is selected

- XDGDATA/mime/packages/cst-model.xml

will be created and

- update-mime-database

is called to register MIME types for CST project files. This is according to

• ”shared MIME database” and• ”MIME run actions”

5. If the [MC] or [SS] option is selected, settings for Solver Server and Main Controllerwill be written to

- "/etc/xdg/CST AG/"

These settings can be changed with ”CST DC Solver Control” or ”CST DC MainControl” or a text editor. Please refer to the Online Help of CST STUDIO SUITE™for a detailed description of the distributed computing options.

6. Files in the installation directory and the configuration files in /etc/xdg/CST AG/will get the ”Main User” (chosen during installation) as owner.

7. The installed daemons will be started via the /etc/init.d scripts. Both DC serviceswill automatically generate working directories in /tmp if [MC] or [SS] was selected:

- /tmp/CSTMainControllerWork2014- /tmp/CSTSolverServerWork2014

B Installation on Unsupported DistributionsCST officially supports RedHat Enterprise Linux (RHEL) version 5.x, 6.x and SUSE LinuxEnterprise Server (SLES) 11. We strongly recommend using CST software on these sup-ported distributions. However, if you need to use the CST software on a Linux distribu-tion that is not officially supported this section of the document contains some informationwhich may help you to setup the software successfully. The instructions apply to the 64-bit(x86_64) versions of the distributions.

February 11, 2014 28

B.1 Debian 6 (64-bit)The following packages must be installed prior to installation:

xvfb util-linux ia32-libs lib32gcc1 lib32stdc++6 lib32z1 libc6-i386lesstif2 libc6 libdrm2 libexpat1 libfontconfig1 libfreetype6 libgcc1libgl1-mesa-glx libglu1-mesa libglw1-mesa libice6 libjpeg62libpng12-0 libsm6 libstdc++6 libuuid1 libx11-6 libxau6 libxcb1libxdamage1 libxdmcp6 libxext6 libxfixes3 libxi6 libxp6 libxpm4libxrender1 libxt6 libxxf86vm1 zlib1g python rpm

B.2 Ubuntu 12.04 (64-bit)The following packages must be installed prior to installation:

xvfb util-linux ia32-libs lib32gcc1 lib32z1 libc6-i386 libc6 libdrm2libexpat1 libfontconfig1 libfreetype6 libgcc1 libgl1-mesa-glxlibglu1-mesa libice6 libjpeg62 libpng12-0 libsm6 libstdc++6 libuuid1libx11-6 libxau6 libxcb1 libxdamage1 libxdmcp6 libxext6 libxfixes3libxi6 libxp6 libxpm4 libxrender1 libxt6 libxxf86vm1 zlib1gpython rpm

February 11, 2014 29