Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] Convert to Synchronized project using remote xlC compiler toolchain

The problem could be that perhaps you are copying the scanner discovery profile/profileID from the local config. The remote config should have a remote discovery profile.

The compiler path in the XLC page is a resource property on the project, if I recall.

===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto

Inactive hide details for John Eblen ---09/21/2011 12:58:25 PM---The conversion wizard copies the settings of the active configJohn Eblen ---09/21/2011 12:58:25 PM---The conversion wizard copies the settings of the active configuration when creating the Remote confi


From:

John Eblen <jeblen@xxxxxxx>

To:

Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>

Date:

09/21/2011 12:58 PM

Subject:

Re: [ptp-dev] Convert to Synchronized project using remote xlC compiler toolchain

Sent by:

ptp-dev-bounces@xxxxxxxxxxx




The conversion wizard copies the settings of the active configuration when creating the Remote configuration. Inside C/C++ Build you can then change the settings for Remote. Oddly, though, the XL C/C++ compiler page does not allow you to select a configuration. So I don't know which configurations are altered when this is changed.

On Wed, Sep 21, 2011 at 11:39 AM, Beth Tibbitts <tibbitts@xxxxxxxxxx> wrote:
    I'm having trouble converting a local C/C++ project to a sync project that needs the xlC toolchain on the remote system.
    I made the original local project specify the xlC/C++ toolchain (not remote).  The remote machine is Linux.
        I did not modify the default locations of xlc or the version
    It's an MPI program, not that it matters.  "Shallow" our typical PTP tutorial exercise.
    when i convert it, get the makefile to get called and no build errors,

    I have the remote project building
    but am getting some errors like "Cannot run program '/xlc' and 'xlC' "  
    and what looks like some other problems.
    Any ideas?
    I do not get this problem when i specify e.g. Mac GCC toolchain on the local project, then the remote system in Linux and GCC.
    l

    I still get the above even If I change project properties, C/C++ Build, XlC/C++ compiler, compiler root path to be correct.
    (xlC is in my path and can be found by command line on the remote sys)
    This part of project properties looked like it dealt with local only, but does the sync project take it to use it?

    It does appear to have built ok, i have .o's and executable.

    Any idea what's going on?


    ...Beth

    Beth Tibbitts
    Eclipse Parallel Tools Platform  
    http://eclipse.org/ptp
    IBM STG - High Performance Computing Tools
    Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511


    _______________________________________________
    ptp-dev mailing list

    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


GIF image

GIF image

JPEG image


Back to the top