See the [http://eclipse.org/ptp/downloads.php PTP download page]; check regularly there for new releases, too.

See the [http://eclipse.org/ptp/downloads.php PTP download page]; check regularly there for new releases, too.

Line 8:

Line 8:

See the [[PTP/release_notes/6.0|PTP 6.0 release notes]] for detailed instructions on how to install PTP.

See the [[PTP/release_notes/6.0|PTP 6.0 release notes]] for detailed instructions on how to install PTP.

+

+

==Q: How do find out more about Synchronized Projects and System Monitoring? ==

+

+

There are other FAQ pages with Frequently asked questions about

+

* [[PTP/sync-projects#FAQ| PTP Synchronized Projects]] and

+

* [[PTP/System_Monitoring_FAQ|PTP System Monitoring]]

== Q: What version of Eclipse and CDT do I need? ==

== Q: What version of Eclipse and CDT do I need? ==

−

PTP 5.0 is designed to work with Eclipse 4.2 (Juno) and CDT 8.1.x. (The all-in-package referenced above now takes care of this for you.)

+

PTP 6.0 is designed to work with Eclipse 4.2 (Juno) and CDT 8.1.x. (The all-in-package referenced above now takes care of this for you.)

PTP 5.0 is designed to work with Eclipse 3.7.x (Indigo) and CDT 8.0.x. (The all-in-package referenced above now takes care of this for you.)

PTP 5.0 is designed to work with Eclipse 3.7.x (Indigo) and CDT 8.0.x. (The all-in-package referenced above now takes care of this for you.)

Line 23:

Line 29:

PTP supports the following MPI runtimes:

PTP supports the following MPI runtimes:

−

* Open MPI 1.2.x, 1.3.x, or 1.4.x

+

* Open MPI 1.2.x, 1.3.x, or 1.4.x ... and higher.

* MPICH2 1.0.6p1

* MPICH2 1.0.6p1

* IBM's Parallel Environment (PE)

* IBM's Parallel Environment (PE)

−

The most recent OpenMPI (1.4.x) is recommended for PTP 4.0.x and 5.0.x, although it may work with older releases.

+

The most recent OpenMPI (generally) is recommended for the most recent release of PTP, although it may work with older releases.

−

For the Parallel Language Development Tools only, there should be no difference between the different versions of MPI, such as OpenMPI and LamMPI. You just need to configure your project to be built using mpicc rather than gcc (for MPI releases that require that; most do), and to specify the include path to the MPI header files. This should be described in the [http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.ptp.pldt.doc.user%2Fhtml%2Ftoc.html PLDT help].

+

For the Parallel Language Development Tools only, there should be no difference between the different versions of MPI, such as OpenMPI and LamMPI. You just need to configure your project to be built using mpicc rather than gcc (for MPI releases that require that; most do), and to (optionally) specify the include path to the MPI header files. This should be described in the [http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.ptp.pldt.doc.user%2Fhtml%2Ftoc.html PLDT help].

== Q: What platforms and runtimes are supported by PTP now? ==

== Q: What platforms and runtimes are supported by PTP now? ==

Line 55:

Line 61:

At this point it's a good idea to run a small mpi program to test you have installed Open MPI correctly.

At this point it's a good idea to run a small mpi program to test you have installed Open MPI correctly.

−

mpicc -o testMPI testMPI.c

+

mpicc -o testMPI testMPI.c

−

mpirun -np 2 testMPI

+

mpirun -np 2 testMPI

== Q: How do I build PTP myself? ==

== Q: How do I build PTP myself? ==

Line 78:

Line 84:

== Q: What's the most recent version of PTP? ==

== Q: What's the most recent version of PTP? ==

−

The current released version is 5.0.x.

+

The current released version is 6.0.x. (Fall 2012 )

−

See the announcements on http://eclipse.org/ptp which should indicate the latest release number. As of October 18, 2011 this is 5.0.3.

+

See the announcements on http://eclipse.org/ptp which should indicate the latest release number. As of December 2012 this is 6.0.4.

−

The most accurate latest release number is whatever is found on the update site at http://download.eclipse.org/tools/ptp/updates/indigo.

+

The most accurate latest release number is whatever is found on the update site at http://download.eclipse.org/tools/ptp/updates/juno

<span id="update_ptp_specific"></span>

<span id="update_ptp_specific"></span>

Line 93:

Line 99:

There are two update sites:

There are two update sites:

−

*The Eclipse Juno update site http://download.eclipse.org/releases/juno contains all the Eclipse projects (as of June 27, 2012 it contains PTP 6.0.0)

+

*The Eclipse Juno update site http://download.eclipse.org/releases/juno contains all the Eclipse projects (as of March 1, 2013 it contains PTP 6.0.4)

−

*The PTP-specific update site http://download.eclipse.org/tools/ptp/updates/juno may have a more recent release (As of June 29, 2012 it contains PTP 6.0.1)

+

*The PTP-specific update site http://download.eclipse.org/tools/ptp/updates/juno may have a more recent release (As of March 15, 2013 it contains PTP 6.0.5)

: <b>Update Sites</b>

: <b>Update Sites</b>

Line 119:

Line 125:

== Q: I want to live a bit on the bleeding edge. How do I install a more recent PTP build, e.g. to get a bug fix ? ==

== Q: I want to live a bit on the bleeding edge. How do I install a more recent PTP build, e.g. to get a bug fix ? ==

−

Go to the [[PTP/builds|PTP builds page]] and find the page for your release (e.g. if you have 4.0.x, find the page with the largest value of x) and download the archive

+

Go to the [[PTP/builds|PTP builds page]] and find the page for your release (e.g. if you have 6.0.x, find the page with the largest value of x) and download the archive

file (ptp-master-xxx) then use that in the Help > Install New Software... dialog.

file (ptp-master-xxx) then use that in the Help > Install New Software... dialog.

Line 125:

Line 131:

Open Preferences (Window > Preferences or on a Mac, Eclipse > Preferences), Open Run/Debug / Launching

Open Preferences (Window > Preferences or on a Mac, Eclipse > Preferences), Open Run/Debug / Launching

−

Under "General Options" on that page, Uncheck "Build (if required) before launching"

== Q: How do I create my own Target System Configuration (TSC) for the scheduler on my remote system ? ==

+

+

See the next Q - where TSCs are referred to as "Resource Managers"

== Q: How do I customize the new (JAXB) Configurable Resource Manager? ==

== Q: How do I customize the new (JAXB) Configurable Resource Manager? ==

+

+

(Note: Target System Configurations were previously called "Resource Managers" in previous releases of PTP. Not all terminology has been changed here.)

A detailed guide to the XML Schema for the new Configurable Resource Manager, along with an introductory tutorial slide-set demonstrating some simple modifications to an existing XML definition, are now available at [[PTP/resource-managers]].

A detailed guide to the XML Schema for the new Configurable Resource Manager, along with an introductory tutorial slide-set demonstrating some simple modifications to an existing XML definition, are now available at [[PTP/resource-managers]].

−

To take an existing JAXB-based resource manager and be able to tweak it, you can import it and change the xml data yourself. To do this:

+

To take an existing JAXB-based resource manager (a.k.a. TSC) and be able to tweak it, you can import it and change the xml data yourself. To do this:

* Go to Import..., then open Resource Managers>Resource Manager Definition From Plug-in.

* Go to Import..., then open Resource Managers>Resource Manager Definition From Plug-in.

* Choose the Resource Manager you want to clone (e.g. PBS-Generic-Batch) RM from the combo.

* Choose the Resource Manager you want to clone (e.g. PBS-Generic-Batch) RM from the combo.

* This should create a new project in your workspace called resourceManagers.

* This should create a new project in your workspace called resourceManagers.

−

* Expand the resourceManagers folder created. The ''name of the file'' is what the 'name' of the Resource manager is derived from. Rename it if you like. Spaces in the name are OK, e.g "My RM.xml"

+

* Expand the resourceManagers folder created.

* Double click on the xml file to open it in an editor.

* Double click on the xml file to open it in an editor.

+

* Change the name in the xml attribute "name=" to be something unique.

* Example of a PBS change: Go to the end of the file, and change line 828 from '<monitor-data schedulerType="TORQUE">' to '<monitor-data schedulerType="PBS">'.

* Example of a PBS change: Go to the end of the file, and change line 828 from '<monitor-data schedulerType="TORQUE">' to '<monitor-data schedulerType="PBS">'.

* Save the file.

* Save the file.

−

Now, to use the new Resource Manager

+

Now, to use the new TSC/Resource Manager

−

* Go to the System Monitoring perspective and add a new RM.

+

* Launch a Parallel Application and select your new TSC.

−

* Use the definition you just edited (should have "(1)" after the name, unless you renamed the file).

+

If you're planning to change the XML after you have used it to create a RM,

If you're planning to change the XML after you have used it to create a RM,

Line 148:

Line 161:

* Check the "Always load XML from URL" option.

* Check the "Always load XML from URL" option.

* Stopping and restarting the RM will then reload the new definition.

* Stopping and restarting the RM will then reload the new definition.

+

+

More information:

+

* http://wiki.eclipse.org/PTP/workshops/September_2012 includes several presentations on related topics

+

** [http://wiki.eclipse.org/images/f/fc/PTPUserDev2012_JAXB.pdf Adding Support for a new Resource Manager]

+

** [http://wiki.eclipse.org/images/d/d0/PTPUserDev2012_Monitoring_Karbach_Frings.pdf Monitoring system basics, and adding support for a new batch system ]

== Q: How do I enable the Eclipse menu icons to show in Linux with GTK? ==

== Q: How do I enable the Eclipse menu icons to show in Linux with GTK? ==

Line 155:

Line 173:

== Q: How do I use PTP to connect to a remote system via an intermediate host (multi hop) ==

== Q: How do I use PTP to connect to a remote system via an intermediate host (multi hop) ==

where <intermediate-host> is the host name of the intermediate system and <target-host> is the host name of the target system. The first port number (22222) can be any port number greater than 1024 that is not already being used. Use <intermediate-userid>@ if the userid is different from your local system. The second port number must be 22. Once a connection is established to <intermediate-host>, you will need to leave this session connected while you're using PTP. In the resulting session, if you issue the command 'hostname' you should see the value for the intermediate-host system.

+

where <intermediate-host> is the host name of the intermediate system and <target-host> is the host name of the target system. The first port number (22222) can be any port number greater than 1024 that is not already being used on your local system. Use <intermediate-userid>@ if the userid is different from your local system. The second port number must be 22. Once a connection is established to <intermediate-host>, you will need to leave this session connected while you're using PTP. In the resulting session, if you issue the command 'hostname' you should see the value for the intermediate-host system.

−

Next, when you configure a new resource manager, create a new connection (using Remote Tools) and specify the host name as 'localhost'. Click on the 'Advanced' button, and change the port number from 22 to the number you specified in the command above.

+

Next, when you create a new connection - specify the host name as 'localhost'. Click on the 'Advanced' button, and change the port number from 22 to the number you specified in the command above.

Use this same connection when configuring a remote or synchronized project.

Use this same connection when configuring a remote or synchronized project.

Line 173:

Line 191:

And in the resulting session, the command 'hostname' should match the target-host system.

And in the resulting session, the command 'hostname' should match the target-host system.

== Q: Eclipse complains "No such file or directory" when attempting a remote build for a managed project ==

+

+

Managed projects create their build directories. By default they are called "Debug_remote" or "Release_remote." These are created locally and then replicated to the remote host. Please check your replication filter settings and make sure that at least the makefile and make include files in these directories are being transferred to the remote side.

If you are starting Eclipse from a Linux window manager (Gnome, KDE, etc.) then consult your window manager documentation for information on how to set environment variables.

If you are starting Eclipse from a Linux window manager (Gnome, KDE, etc.) then consult your window manager documentation for information on how to set environment variables.

−

If you are starting Eclipse from the MacOS X window manager (Aqua), the PATH must be set by creating a file called environment.plist in a directory called .MacOSX in your home directory.

+

If you are starting Eclipse from the OS X window manager, the solution depends on the version of OS X.

−

The file should look like this, with [path_to_something] replaced with the correct path:

+

+

<b>For OS X 10.7 (Lion) and earlier: </b>

+

+

PATH must be set by creating a file called <code>environment.plist</code> in a directory called <code>.MacOSX</code> in your home directory.

+

The file should look like this, with [path_from_shell] replaced with the correct path, such as that obtained by the command "echo $PATH" in your shell.

<pre>

<pre>

<?xml version="1.0" encoding="UTF-8"?>

<?xml version="1.0" encoding="UTF-8"?>

Line 198:

Line 228:

<dict>

<dict>

<key>PATH</key>

<key>PATH</key>

−

<string>[path_to_something]</string>

+

<string>[path_from_shell]</string>

</dict>

</dict>

</plist>

</plist>

−

</pre>

</pre>

+

+

<b> For OS X 10.8 (Mountain Lion):</b>

+

+

The <code>environment.plist</code> method no longer works. Instead you have two choices:

+

# Modify the environment for all applications globally. This is done by using the command 'launchctl setenv key value'. You will need to restart the application for the new environment to be picked up. Note that this only lasts until the next reboot. For a permanent fix, edit <code>/etc/launchd.conf</code> and add a 'setenv' line.

+

# Modify the environment for the specific application. This involves editing the application <code>Info.plist</code> and adding an 'LSEnvironment' key. See [http://developer.apple.com/library/ios/#documentation/general/Reference/InfoPlistKeyReference/Articles/LaunchServicesKeys.html LaunchServicesKeys] for more information.

+

+

There are also tools such as [http://diaryproducts.net/EnvPane EnvPane] which may be helpful, and a good discussion [http://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x here].

== Q. When dealing with my remote system I see an error "Invalid java version or java not installed on "<connection name>"" ==

== Q. When dealing with my remote system I see an error "Invalid java version or java not installed on "<connection name>"" ==

Line 209:

Line 246:

Remote projects (not synchronized projects) need java on the remote system in order to start the indexing service. So make sure java is in your PATH, and it is accessible from a non-interactive shell (see next FAQ item).

Remote projects (not synchronized projects) need java on the remote system in order to start the indexing service. So make sure java is in your PATH, and it is accessible from a non-interactive shell (see next FAQ item).

+

+

== Q: How can I get the C/C++ indexer to use my remote include paths in a synchronized project? ==

+

+

Even if you have your project set to use a remote build configuration that contains the paths to the remote include files, the C/C++ indexer may find include files on the local (client) machine instead of the remote machine.

+

+

The problem here is the settings for the indexer itself. To fix this, you must set the indexer to use the active build configuration, instead of the default, which is usually the local build config. A further complication is that because of a bug in the indexer project settings, any change you make to it will not be preserved when you restart Eclipse (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=205299 bug205299]). Fortunately, there is a simple work around: use the global settings for the C/C++ indexer instead of the project-specific settings; the global setting ''is'' preserved across restarts of Eclipse. To change this setting, use Window->Preferences->C/C++->Indexer then check "Use active build configuration".

This is because Lion has introduced new security requirements for gdb to work. [http://sourceware.org/gdb/wiki/BuildingOnDarwin This article] describes the problem and solution in more detail. Note that gdb is installed by default as /usr/libexec/gdb/gdb-i386-apple-darwin. The /usr/bin/gdb command is just a script that invokes this executable.

+

This is because Lion has introduced new security requirements for gdb to work. Note that gdb is installed by default as /usr/libexec/gdb/gdb-i386-apple-darwin. The /usr/bin/gdb command is just a script that invokes this executable.

−

The simplest solution is to execute the following commands (this assumes that your user is in the procmod group, check using the 'id' command):

+

=== Lion ===

+

+

Execute the following commands (this assumes that your user is in the procmod group, check using the 'id' command):

chgrp procmod /usr/libexec/gdb/gdb-i386-apple-darwin

chgrp procmod /usr/libexec/gdb/gdb-i386-apple-darwin

chmod g+s /usr/libexec/gdb/gdb-i386-apple-darwin

chmod g+s /usr/libexec/gdb/gdb-i386-apple-darwin

+

+

=== Mountain Lion ===

+

+

Running the following command appears to work:

+

+

sudo DevToolsSecurity -enable

== Q: I get the message 'Unable to determine gdb version' when trying to debug a program ==

== Q: I get the message 'Unable to determine gdb version' when trying to debug a program ==

Line 266:

Line 318:

Make sure you have the "Path to backend debugger" preference set to the path to the gdb program, not the sdm. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368312 this bug] for more details.

Make sure you have the "Path to backend debugger" preference set to the path to the gdb program, not the sdm. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368312 this bug] for more details.

−

...

+

== Q: How do I debug the server part of PTP's system monitoring capability? ==

+

If the Active Jobs view is empty when you know jobs are running on the system, perhaps the commands queried from the monitoring system are not successful.

+

+

1. On the remote machine, go to the ".eclipsesettings" directory, located in your home directory

+

+

2. Create a file called ".LML_da_options" containing a single line "keeptmp=1" (no quotes).

+

+

3. Restart the monitor.

+

+

4. You should now find a directory called "tmp_<hostname>_<pid>" in the ".eclipsesettings" directory. It should contain an error log file, plus a bunch of other files. Check these files to see if you can see the cause of the error.

+

+

5. Remember to remove the ".LML_da_options" file once you have finished.

+

+

See also [[PTP/System_Monitoring_FAQ | PTP System Monitoring FAQ]]

+

+

== Q: What do I do when i get "Failed to Create the Java Virtual Machine" launching on win32? ==

+

+

The JVM cannot allocate enough memory with current eclipse settings.

+

FInd your eclipse.ini file (in the same directory as the eclipse executable), and in the line e.g.

+

-Xmx2048m ==> change it to a smaller number e.g. to -Xmx512m or -Xmx768m or -Xmx1024m

+

+

It could be that your eclipse will run out of memory on a machine with a relatively small amount of RAM.

+

(Need to publish suggested memory minimums.)

+

+

Note that a 32bit windows app only can have 2GB memory total. Changing the -Xms and -Xmx values to:

+

-Xms512m

+

-Xmx1536m

+

may fix it (assuming your machine tolerates *that* much). Older machines, or with less memory, may need to go down to

Q: How do find out more about Synchronized Projects and System Monitoring?

Q: What version of Eclipse and CDT do I need?

PTP 6.0 is designed to work with Eclipse 4.2 (Juno) and CDT 8.1.x. (The all-in-package referenced above now takes care of this for you.)

PTP 5.0 is designed to work with Eclipse 3.7.x (Indigo) and CDT 8.0.x. (The all-in-package referenced above now takes care of this for you.)

PTP 4.0 is designed to work with Eclipse 3.6.x (Helios) and CDT 7.0.x.

PTP 3.0 is designed to work with Eclipse 3.5.x (Galileo) and CDT 6.0.2.

Q: What version of MPI do I need to run PTP?

PTP supports the following MPI runtimes:

Open MPI 1.2.x, 1.3.x, or 1.4.x ... and higher.

MPICH2 1.0.6p1

IBM's Parallel Environment (PE)

The most recent OpenMPI (generally) is recommended for the most recent release of PTP, although it may work with older releases.

For the Parallel Language Development Tools only, there should be no difference between the different versions of MPI, such as OpenMPI and LamMPI. You just need to configure your project to be built using mpicc rather than gcc (for MPI releases that require that; most do), and to (optionally) specify the include path to the MPI header files. This should be described in the PLDT help.

Q: What platforms and runtimes are supported by PTP now?

The current release of PTP runs on Linux, MacOS X, and Windows. PTP only supports target systems running Linux, MacOS X, and some kinds of Unix (e.g. AIX).

The Parallel Language Development Tools will run anywhere Eclipse and CDT will run. It may require a version of MPI (specifically, its header files) to aid in the search for MPI artifacts. And an OpenMP header file, if OpenMP analysis is needed. This means you can develop and analyze source files but you can't launch them.

The Remote Development Tools can be used on Linux, MacOS X, and Windows.

Q: How do I install Open MPI?

You may already have it installed. Try running the following command and check the output:

ompi_info

If this doesn't work, download the latest version from the Open MPI site.

Unpack the distribution and run the commands (note that you may have to add extra options to configure to suit your local site - see the Open MPI help documentation for more information):

./configure --prefix=/path/to/your/ompi/install
make
make install

At this point it's a good idea to run a small mpi program to test you have installed Open MPI correctly.

mpicc -o testMPI testMPI.c
mpirun -np 2 testMPI

Q: How do I build PTP myself?

Q: How do I ask questions about PTP?

Subscribe to the PTP Mailing lists, especially ptp-user, and ask questions there.
This is an excellent place to ask new-user questions.
The ptp-user list is watched by most of our PTP developers as well as many users,
and you can share in their experience. See http://www.eclipse.org/ptp/mailing_lists.php

The Juno update site (http://download.eclipse.org/releases/juno) contains the last release of PTP that was built into the Eclipse general update site. Eclipse Juno updates are released only in September and February. This update site (a.k.a. software repository) is enabled by default when you install Eclipse Juno (a.k.a. 4.2).

Help > Install New Software.... and install PTP from there

Help > Check for Updates will find the updates for all your installed features that are found there.

PTP maintains its own PTP-specific update site with the most recent release of PTP. Bug fix releases can be more frequent than the main Eclipse. You must enable the PTP-specific update site before the updates will be found.

Q: How do I update my PTP within the package "Eclipse IDE for Parallel Application Developers" ?

Q: I want to live a bit on the bleeding edge. How do I install a more recent PTP build, e.g. to get a bug fix ?

Go to the PTP builds page and find the page for your release (e.g. if you have 6.0.x, find the page with the largest value of x) and download the archive
file (ptp-master-xxx) then use that in the Help > Install New Software... dialog.

Q: When I launch a parallel job how do I stop it from building everything in my workspace ?

Open Preferences (Window > Preferences or on a Mac, Eclipse > Preferences), Open Run/Debug / Launching

Q: How do I create my own Target System Configuration (TSC) for the scheduler on my remote system ?

See the next Q - where TSCs are referred to as "Resource Managers"

Q: How do I customize the new (JAXB) Configurable Resource Manager?

(Note: Target System Configurations were previously called "Resource Managers" in previous releases of PTP. Not all terminology has been changed here.)

A detailed guide to the XML Schema for the new Configurable Resource Manager, along with an introductory tutorial slide-set demonstrating some simple modifications to an existing XML definition, are now available at PTP/resource-managers.

To take an existing JAXB-based resource manager (a.k.a. TSC) and be able to tweak it, you can import it and change the xml data yourself. To do this:

Go to Import..., then open Resource Managers>Resource Manager Definition From Plug-in.

Choose the Resource Manager you want to clone (e.g. PBS-Generic-Batch) RM from the combo.

This should create a new project in your workspace called resourceManagers.

Expand the resourceManagers folder created.

Double click on the xml file to open it in an editor.

Change the name in the xml attribute "name=" to be something unique.

Example of a PBS change: Go to the end of the file, and change line 828 from '<monitor-data schedulerType="TORQUE">' to '<monitor-data schedulerType="PBS">'.

Save the file.

Now, to use the new TSC/Resource Manager

Launch a Parallel Application and select your new TSC.

If you're planning to change the XML after you have used it to create a RM,

Q: How do I use PTP to connect to a remote system via an intermediate host (multi hop)

where <intermediate-host> is the host name of the intermediate system and <target-host> is the host name of the target system. The first port number (22222) can be any port number greater than 1024 that is not already being used on your local system. Use <intermediate-userid>@ if the userid is different from your local system. The second port number must be 22. Once a connection is established to <intermediate-host>, you will need to leave this session connected while you're using PTP. In the resulting session, if you issue the command 'hostname' you should see the value for the intermediate-host system.

Next, when you create a new connection - specify the host name as 'localhost'. Click on the 'Advanced' button, and change the port number from 22 to the number you specified in the command above.

Use this same connection when configuring a remote or synchronized project.

Sample Confirmation

As a confirmation of the tunneling being set up correctly, you can do the following in another terminal window:

ssh -p 22222 <target-userid>@localhost

And in the resulting session, the command 'hostname' should match the target-host system.

Q: Eclipse complains "No such file or directory" when attempting a remote build for a managed project

Managed projects create their build directories. By default they are called "Debug_remote" or "Release_remote." These are created locally and then replicated to the remote host. Please check your replication filter settings and make sure that at least the makefile and make include files in these directories are being transferred to the remote side.

Q: Eclipse doesn't seem to find commands for [compiler, make, ...]

If you get an error, e.g. in the console, saying something cannot be found, such as:

error
/bin/sh: ifort: not found
make: *** [test.o] Error 127

Then it likely means that the required command cannot be found in your PATH environment variable, e.g. ifort in this case.

If you are starting Eclipse from a shell make sure the path to the command is specified for the PATH environment variable in your login script.
(Note: reference interactive shell vs. non-interactive shell below in next FAQ item)

If you are starting Eclipse from a Linux window manager (Gnome, KDE, etc.) then consult your window manager documentation for information on how to set environment variables.

If you are starting Eclipse from the OS X window manager, the solution depends on the version of OS X.

For OS X 10.7 (Lion) and earlier:

PATH must be set by creating a file called environment.plist in a directory called .MacOSX in your home directory.
The file should look like this, with [path_from_shell] replaced with the correct path, such as that obtained by the command "echo $PATH" in your shell.

The environment.plist method no longer works. Instead you have two choices:

Modify the environment for all applications globally. This is done by using the command 'launchctl setenv key value'. You will need to restart the application for the new environment to be picked up. Note that this only lasts until the next reboot. For a permanent fix, edit /etc/launchd.conf and add a 'setenv' line.

Modify the environment for the specific application. This involves editing the application Info.plist and adding an 'LSEnvironment' key. See LaunchServicesKeys for more information.

There are also tools such as EnvPane which may be helpful, and a good discussion here.

Q. When dealing with my remote system I see an error "Invalid java version or java not installed on "<connection name>""

See the other FAQ items about environment variables. Your userid isn't finding Java in your path.

Remote projects (not synchronized projects) need java on the remote system in order to start the indexing service. So make sure java is in your PATH, and it is accessible from a non-interactive shell (see next FAQ item).

Q: How can I get the C/C++ indexer to use my remote include paths in a synchronized project?

Even if you have your project set to use a remote build configuration that contains the paths to the remote include files, the C/C++ indexer may find include files on the local (client) machine instead of the remote machine.

The problem here is the settings for the indexer itself. To fix this, you must set the indexer to use the active build configuration, instead of the default, which is usually the local build config. A further complication is that because of a bug in the indexer project settings, any change you make to it will not be preserved when you restart Eclipse (see bug205299). Fortunately, there is a simple work around: use the global settings for the C/C++ indexer instead of the project-specific settings; the global setting is preserved across restarts of Eclipse. To change this setting, use Window->Preferences->C/C++->Indexer then check "Use active build configuration".

Your environment may be set up correctly for an interactive shell but not for a non-interactive shell. You probably want to set up
the same environment for an interactive and non-interactive shell.
For example, for bash, there are at least two files ~/.profile and ~/.bashrc. Make sure you know which ones your system uses. Naturally this depends upon what shell you are running.

~/.profile or .bash_profile– read by ssh in interactive shell on login

~/.bashrc – read by ssh in non-interactive shell on login

Make sure the non-interactive shell is set up properly. Perhaps helpful reference(s):

This is because Lion has introduced new security requirements for gdb to work. Note that gdb is installed by default as /usr/libexec/gdb/gdb-i386-apple-darwin. The /usr/bin/gdb command is just a script that invokes this executable.

Lion

Execute the following commands (this assumes that your user is in the procmod group, check using the 'id' command):

Mountain Lion

Q: I get the message 'Unable to determine gdb version' when trying to debug a program

Make sure you have the "Path to backend debugger" preference set to the path to the gdb program, not the sdm. See this bug for more details.

Q: How do I debug the server part of PTP's system monitoring capability?

If the Active Jobs view is empty when you know jobs are running on the system, perhaps the commands queried from the monitoring system are not successful.

1. On the remote machine, go to the ".eclipsesettings" directory, located in your home directory

2. Create a file called ".LML_da_options" containing a single line "keeptmp=1" (no quotes).

3. Restart the monitor.

4. You should now find a directory called "tmp_<hostname>_<pid>" in the ".eclipsesettings" directory. It should contain an error log file, plus a bunch of other files. Check these files to see if you can see the cause of the error.

5. Remember to remove the ".LML_da_options" file once you have finished.

Q: What do I do when i get "Failed to Create the Java Virtual Machine" launching on win32?

The JVM cannot allocate enough memory with current eclipse settings.
FInd your eclipse.ini file (in the same directory as the eclipse executable), and in the line e.g.
-Xmx2048m ==> change it to a smaller number e.g. to -Xmx512m or -Xmx768m or -Xmx1024m

It could be that your eclipse will run out of memory on a machine with a relatively small amount of RAM.
(Need to publish suggested memory minimums.)

Note that a 32bit windows app only can have 2GB memory total. Changing the -Xms and -Xmx values to:

-Xms512m
-Xmx1536m

may fix it (assuming your machine tolerates *that* much). Older machines, or with less memory, may need to go down to