| Re: [ptp-user] wizard didn't accomplish a PTP synchronized project |
|
On Saturday, December 08, 2012 12:00:07 Christoph Pospiech wrote: > Hi, > > I just had a single source file, so I tried the wizard > New -> Synchronized C/C++ project -> > Executable -> MPI Empty C Project. > I chose one local (Linux gcc) and one remote ( XL C/C++) > tool chain....and got a local project with the remote tool chain. > Correcting the local tool chain was easy, but I got stuck when attempting > to activate the remote project. > 1. No remote connection was set up > 2. No build configuration for the remote project was set up > 3. When attempting to add a new build configuration, the Eclipse flagged a > NullPointerException when specifying the remote directory for > synchronization. 4. The project is flagged as "synchronized project", so I > can't use thew wizard New->other->Remote-> Convert C/C++ or Fortran Project > to a synchronized project. > 5. I shut down eclipse, removed the line > <nature>org.eclipse.ptp.rdt.sync.core.remoteSyncNature</nature> > from .project and retried > New->other->Remote-> Convert C/C++ or Fortran Project to a synchronized > project. This worked, but I ended up in the situation described in an > earlier post with subject "PTP wizard entanglement". > > Help !! > > Is there any way to get automatic makefile generation working for PTP > synchronized projects ?
I retried today from scratch after realizing that I might have been too restrictive in setting up the replication filter.
Now I get the remote connection set up OK, also the remote build configuration. Only the local build configuration(s) are missing.
Anyway, I corrected the tool chain settings (was local tool chain for remote project) and PATH settings (were local paths for the remote project). Then I tried to compile remotely, which failed - with the strange error message that the command "echo" was unknown :-(
I enforced that the remote command /client/bin/make should be taken, but I got the error message that /client/bin/make is not there. Also I was missing the familiar console output about loading the modules that I had ticked in "Environment Management".
This all looks like make being executed locally rather than remotely. This would be utterly wrong because locally I will get 32-bit ELF executables, but I need 64-bit xcoff executables remotely, and the xlc toolchain is only available remotely.
It appears that the makefile generation happens locally - which is OK. The PTP synchronization replicates this to the correct place. But the make isn't executed as it should be.
Logging in to the remote host via ssh, change directory to Debug_remote as created by PTP synchronization and executing "make" on the command line makes the correct executable (with the makefile and CFLAGS as auto-generated by Eclipse) without any problems.
How to convince eclipse to execute the correct make command ? Any comments welcome !
--
Mit freundlichen Grüßen / Kind regards
Dr. Christoph Pospiech High Performance & Parallel Computing Phone: +49-351 86269826 Mobile: +49-171-765 5871 E-Mail: christoph.pospiech@xxxxxxxxxx ------------------------------------------------------------------------------------------------------------------------------------------- IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Martina Koederitz (Vorsitzende), Reinhard Reschke, Dieter Scholz, Gregor Pillen, Joachim Heel, Christian Noll Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 14562 / WEEE-Reg.-Nr. DE 99369940
|