Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PTP/release notes/2.0"

(FAQ)
(FAQ)
Line 170: Line 170:
  
 
=FAQ=
 
=FAQ=
# Simulating multiple nodes with OpenMPI: If you are testing on a single node, edit <openmpi_install>/etc/openmpi-default-hostfile and add lines containing 'node0', 'node1', etc. Edit /etc/hosts and add a localhost entry for each name you added to the openmpi-default-hostfile. So, for 'node0', add '127.0.0.1 node0' to /etc/hosts. This will simulate a multi-node machine.
+
# Simulating multiple nodes with OpenMPI: If you are testing on a single node, edit <openmpi_install>/etc/openmpi-default-hostfile (default is /usr/local/etc/openmpi-default-hostfile)  and add lines containing 'node0', 'node1', etc. Edit /etc/hosts and add a localhost entry for each name you added to the openmpi-default-hostfile. So, for 'node0', add '127.0.0.1 node0' to /etc/hosts. This will simulate a multi-node machine.
 
# How do I debug my program remotely?
 
# How do I debug my program remotely?
 
#* Currently you must move the executable to the remote target(s) yourself.  The run/debug launch configuration contains an entry for the location, on the remote machine, of the executable to run/debug.  The source in your local machine (running eclipse and PTP) must match the executable on the remote machine for source-level debugging to work correctly.  This will change when CDT more completely handles remote resources, hopefully by CDT 5.0 (summer '08)
 
#* Currently you must move the executable to the remote target(s) yourself.  The run/debug launch configuration contains an entry for the location, on the remote machine, of the executable to run/debug.  The source in your local machine (running eclipse and PTP) must match the executable on the remote machine for source-level debugging to work correctly.  This will change when CDT more completely handles remote resources, hopefully by CDT 5.0 (summer '08)

Revision as of 19:20, 23 January 2008

Currently under construction ...

Prerequisites

  • OS: Linux or Mac OS X 10.4.x or 10.5.x (for PTP Core only; PLDT should run anywhere Eclipse runs, including Windows.)
  • Java 1.5 or later (Note: for Linux, must be Sun or IBM's. See below.)
  • OpenMPI 1.2 (the earlier 1.0.2 version is also supported)
  • Eclipse 3.3 (also known as Europa)
  • CDT 4.0.2
  • gdb 6.3 or later (earlier versions may also work)

Installation

You will need to install Java, OpenMPI, Eclipse, CDT (Eclipse C/C++ Development Tools), and PTP, then build a small platform-specific set of runtime components. The steps are detailed below:

Install Java

Java requirement: If you are using the Linux operating system, download and install either the Sun Java Runtime Environment or the IBM Java Runtime Environment. The version of Java that ships with Linux will not work with PTP. See the Trouble Shooting section for more information.

Install Open MPI

Download and unpack Open MPI 1.2. If you are using a pre-built binary for Open MPI (such as one that is installed as part of a Linux installation), then it must be a developer version. If there is no developer version available, then you will need to build from source instead.

Configure, build and install from source

In the main Open MPI source directory, run the configure command:

       ./configure --with-devel-headers

and any other options required for your installation.

Build and install Open MPI using:

       make install

Note that if you install Open MPI in a nonstandard location, you may need to build PTP differently. See the troubleshooting section below. Make sure that your PATH and LD_LIBRARY_PATH point to appropriate places if necessary also.

Test your MPI installation by running a small MPI job, e.g.

       mpicc test.c -o test
       mpirun -np 4 test

Install Eclipse

Install Eclipse 3.3.x (SDK or Platform Runtime Binary) and CDT 4.0.2 for your architecture. PTP Release 2.0 requires Eclipse 3.3.* (also known as Europa ) and CDT 4.0.2.

There are three choices here:

  1. (easiest) Install Eclipse SDK - e.g. full version ("Classic") and CDT 4.0.2 - if you plan to do Java or Eclipse development, you'll need this.
  2. (lightweight, smaller footprint) Install Eclipse Platform Runtime Binary and CDT 4.0.2 - if you only plan to to C/C++ development, this is all you need. This is about 1/3 to 1/4 the size of the full SDK, and doesn't include the Java or Eclipse Plug-in development parts, which I assume you don't need. The UI is simpler since you don't have all those additional options.
  3. (not currently available; will be easiest and smallest footprint eventually) Install Eclipse IDE for C/C++ development (should be available when Europa Spring maintenance release includes CDT 4.0.3)

(1) Easy way, full Eclipse install

  1. Go to Eclipse downloads and download "Eclipse classic" for your platform. This is the full SDK.

(2) Details for installing platform (light) version

(Note: when the Spring Europa maintenance release is available, this will be a simple "Eclipse IDE for C/C++ developers" but currently (Jan. '08) it doesn't include CDT 4.0.2)

  1. Go to Eclipse downloads and under "Eclipse Classic" click on "All versions".
  2. Click on the link for the latest release (3.3.1.1 as of this writing)
  3. Scroll down to the heading "Platform Runtime Binary" and download the archive for your platform.

Unpack and launch Eclipse

After downloading and extracting Eclipse (zip or tar file), there's nothing else to the installation process. In the extracted folder, simply run the eclipse executable file. It will ask for a workspace location; the default is fine.

Install CDT

Next, install the CDT (C/C++ Development Toolkit). You can do this from the Eclipse UI as follows:

  1. Help > Software Updates > Find and Install...
  2. Select "Search for new features to install", and click "Next"
  3. Select "New Remote site" and enter
  4. Make sure the "CDT update site" item is checked, and select Finish.
  5. Select a mirror site if asked.
  6. When the Update site is loaded you see the "Search Results" dialog.
  7. Expand the "CDT update site" item, expand "CDT Main Features" and check at least the "C and C++ Development Tools" item.
    • Check any other optional items you like.
  8. Click Next, accept the license terms, Click Next, and click Finish.
    • Eclipse proceeds to download the components you selected.
  9. On the Verification page, click "Install All."
  10. When it's done, click "Yes" to restart the Eclipse workbench.

Install PTP

Install PTP from the Eclipse UI as follows:

  1. Help > Software Updates > Find and Install...
  2. Select "Search for new features to install", and click "Next"
  3. Select "New Remote site" and enter
  4. Make sure the "PTP Update site " item is checked, (you can uncheck CDT if you already installed it and retarted eclipse) and select Finish.
  5. Select a mirror site if asked.
  6. When the Update site is loaded you see the "Search Results" dialog.
  7. Expand the "PTP Update site" item, expand "Parallel Tools Platform 2.0" and check the features you want:
    • Parallel Tools Platform End-User Runtime (required)
    • PTP Parallel Language Development Tools (optional, but recommended)
    • PTP Common External Components (required, platform-specific fragments, proxy & util libraries)
    • PTP Remote Tools Enabler (optional for remote, must have PTP Remote Tools installed)
    • PTP RSE Enabler (optional for remote, must have RSE installed )
    • PTP Support for Open MPI (optional, required to use Open MPI as Resource Manager)
    • PTP Support for IBM Parallel Environment (optional, required to use IBM PE as Resource Manager)
    • PTP Support for IBM LoadLeveler (optional, required to use IBM LL as Resource Manager)
    • PTP Remote Tools (optional)
  8. Click Next, accept the license terms, Click Next, and click Finish.
    • Eclipse proceeds to download the components you selected.
  9. On the Verification page, click "Install All."
  10. When it's done, click "Yes" to restart the Eclipse workbench.

Installation Examples

User wishes to use PTP with the parallel language development tools, and use Remote Tools for remote access. Parallel jobs will be submitted using OpenMPI. Select the following components:

  • Parallel Tools Platform End-User Runtime
  • PTP Parallel Language Development Tools
  • PTP Common External Components
  • PTP Remote Tools Enabler
  • PTP Support for Open MPI
  • PTP Remote Tools

User wishes to use PTP directly on a machine with LoadLeveler installed (no remote services required). PLDT is not required. Select the following components:

  • Parallel Tools Platform End-User Runtime
  • PTP Common External Components
  • PTP Support for IBM LoadLeveler

Users wishes to use PTP with a remote machine that has IBM PE installed. PLDT is required. RSE has already been installed in Eclipse. Select the following components:

  • Parallel Tools Platform End-User Runtime
  • PTP Parallel Language Development Tools
  • PTP Common External Components
  • PTP RSE Enabler
  • PTP Support for IBM Parallel Environment)

User wishes to use Remote Tools only (without PTP). Select the following component:

  • PTP Remote Tools

PTP Setup

Locate the plug-in org.eclipse.ptp.os.arch_x.y.z.### in the plugins directory, where os and arch correspond to your operating system and architecture respectively, x.y.z (if present) corresponds to the release version of that particular plugin, e.g. 2.0.x, and ### corresponds to a possible suffix include the build date etc. For example,

 cd  <eclipse-install-location>/eclipse/plugins/org.eclipse.ptp.linux.x86_2.0.0.200801161606

After changing to this directory, run the build command:

   sh BUILD

This should build and install the executables. If you see any errors here, please refer to the Trouble Shooting section below. If you installed OpenMPI in a non-standard location, see below also for an alternate build command.

Note: be sure that LD_LIBRARY_PATH is set (to point to OpenMPI libs, e.g. /usr/local/lib ) for the environment in which eclipse is launched, and the environment in which the above build is performed. PATH should point to mpi as well, e.g. /usr/local/bin .

Test your installation

Start Eclipse. (You may need to use the -clean parameter to force it to recognize new features and plug-ins).

Create e.g. a small MPI C project. Open the PTP Runtime perspective (Window>Open Perspective>Other...). The runtime service will start and you should see a machine and one or more nodes appear in the 'Machines View'. Add a resource manager and start it. Create a launch configuration (Run -> Open Run Dialog...) and create a launch configuration for a Parallel Application.

More details on using PTP can be found in Help>Help Contents. Click on "PTP: Parallel Tools Platform ". The PTP help is also available online.

Troubleshooting

  1. I get lots of error messages about missing include files when running the BUILD script.
    • This is because OpenMPI was not configured to include the development headers. You need to re-run the configure command for the OpenMPI installation specifying the --with-devel-headers option.
  2. I installed OpenMPI in a non-standard location. Do I need to do anything differently?
    • Yes. The standard location is /usr/local. If you install it to, e.g., /usr/local/openmpi, then when you build the platform-specific PTP code, instead of sh BUILD you should use the following command: CFLAGS=-I/usr/local/openmpi/include LDFLAGS="-L/usr/local/openmpi/lib -Wl,-rpath,/usr/local/openmpi/lib" sh BUILD
  3. When I create a new C project with the new project wizard, nothing happens. The dialog doesn't show.
    • Make sure you have at least CDT 4.0.2 - 4.0.1 and previous builds will not work with the PLDT new project wizards.

See also the the 1.1.1 Release notes troubleshooting section

FAQ

  1. Simulating multiple nodes with OpenMPI: If you are testing on a single node, edit <openmpi_install>/etc/openmpi-default-hostfile (default is /usr/local/etc/openmpi-default-hostfile) and add lines containing 'node0', 'node1', etc. Edit /etc/hosts and add a localhost entry for each name you added to the openmpi-default-hostfile. So, for 'node0', add '127.0.0.1 node0' to /etc/hosts. This will simulate a multi-node machine.
  2. How do I debug my program remotely?
    • Currently you must move the executable to the remote target(s) yourself. The run/debug launch configuration contains an entry for the location, on the remote machine, of the executable to run/debug. The source in your local machine (running eclipse and PTP) must match the executable on the remote machine for source-level debugging to work correctly. This will change when CDT more completely handles remote resources, hopefully by CDT 5.0 (summer '08)

Back to the top