Roland, I can confirm the same behavior with 3.7RC1; this used to work correctly with 3.6.2: /bin/sh: -c: line 0: syntax error near unexpected token `x86' /bin/sh: -c: line 0: `echo "PID=$$ PIID=8" > /dev/pts/21; export "USERPROFILE=C:\Users\jalameda"; export "SystemDrive=C:"; export "Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Common Files\SYSTEM\MSMAPI\1033;C:\Program Files (x86)\QuickTime\QTSystem\;c:\Program Files\Java\jdk1.6.0_18\jre\bin;C:\Program Files (x86)\SSH Communications Security\SSH Secure Shell"; export "PWD=\u\ncsa\jalameda\mpi"; export "PROCESSOR_REVISION=0f06"; export "USERDOMAIN=CARAVELLETDI"; export "MpConfig_AppDataRoot=C:\ProgramData"; export "ALLUSERSPROFILE=C:\ProgramData"; export "SESSIONNAME=Console"; export "TMP=C:\Users\jalameda\AppData\Local\Temp"; export "=::=::\"; export "CWD=\u\ncsa\jalameda\mpi"; export "CommonProgramFiles=C:\Program Files\Common Files"; export "LOGONSERVER=\\CARAVELLETDI"; export "MpConfig_ProductPath=c:\Program Files\Microsoft Security Client\Antimalware"; export "PROCESSOR_LEVEL=6"; export "LOCALAPPDATA=C:\Users\jalameda\AppData\Local"; export "MpConfig_ReportingGUID=7F80789C-2212-4AA1-828D-35E21AA5621C"; export "COMPUTERNAME=CARAVELLETDI"; export "SystemRoot=C:\Windows"; export "asl.log=Destination=file;_OnFirstLog_=command,environment"; export "USERNAME=jalameda"; export "APPDATA=C:\Users\jalameda\AppData\Roaming"; export "ProgramData=C:\ProgramData"; export "PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC"; export "ProgramFiles(x86)=C:\Program Files (x86)"; export "TEMP=C:\Users\jalameda\AppData\Local\Temp"; export "ProgramFiles=C:\Program Files"; export "HOMEDRIVE=C:"; export "QTJAVA=C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip"; export "ProgramW6432=C:\Program Files"; export "PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 15 Stepping 6, GenuineIntel"; export "MpConfig_ProductUserAppDataPath=C:\Users\jalameda\AppData\Local\Microsoft\Microsoft Antimalware"; export "CLASSPATH=.;C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip"; export "MpConfig_ProductAppDataPath=c:\ProgramData\Microsoft\Microsoft Antimalware"; export "PROCESSOR_ARCHITECTURE=AMD64"; export "OS=Windows_NT"; export "FP_NO_HOST_CHECK=NO"; export "HOMEPATH=\Users\jalameda"; export "CommonProgramW6432=C:\Program Files\Common Files"; export "MpConfig_ProductCodeName=Torino"; export "windir=C:\Windows"; export "NUMBER_OF_PROCESSORS=2"; export "PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\"; export "PUBLIC=C:\Users\Public"; export "CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files"; export "ComSpec=C:\Windows\system32\cmd.exe"; cd /u/ncsa/jalameda/mpi; make clean; ' This isn’t pretty. Jay From: ptp-dev-bounces@xxxxxxxxxxx [mailto:ptp-dev-bounces@xxxxxxxxxxx] On Behalf Of Roland Schulz Sent: Tuesday, May 24, 2011 1:49 PM To: Parallel Tools Platform general developers Subject: {Disarmed} [ptp-dev] Fwd: Problem with Linux remote build from Windows 7 client resending because I got an error first time - sorry if you get the email twice. ---------- Forwarded message ---------- From: Roland Schulz <roland@xxxxxxx> Date: Tue, May 24, 2011 at 2:43 PM Subject: Re: [ptp-dev] Problem with Linux remote build from Windows 7 client To: Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
I'm getting the same on Windows. And I don't think it depends on the toolchain. RemoteMakeBuilder line 335 ( remoteEnvMap.putAll(envMap); ) replaces the environment. envMap comes from ManagedBuildManager.getEnvironmentVariableProvider().getVariables(configuration, true). This command returns the local environment variables. Thus the remote environment variables are set to the local environment variables. Because the local environment variables under Windows include odd characters like e.g. parenthesis and RemoteTools doesn't espace those characters correctly one gets this error message: /bin/sh: -c: line 0: syntax error near unexpected token `(' Thus I think this is caused by two problems: - at least in some cases the local environment is exported to the side (which doesn't seem to make sense in any case) - RemoteTools doesn't escape strings correctly before it passes it to /bin/sh On Tue, May 24, 2011 at 1:54 PM, Jay Alameda <jalameda@xxxxxxxxxxxxxxxxx> wrote: Chris,
Here is a png file of the same. The thing I’m intrigued (or troubled by) with Dave’s post was that we are both running windows 7; but the remote environment for me (with 3.6.2) has nothing to do with my local environment. And, I don’t have a local gnu toolchain, I kept my win7 machine intentionally incapable of doing anything remotely useful … Jay Your screenshot is a big red X for me, I don't think it came through. I think the list generally eats screenshots.
"Other toolchain" is just the local GNU toolchain, in disguise. I would use the recently added Remote GNU Toolchain instead. It will grab the environment from the remote system.
=========================== Chris Recoskie Team Lead, IBM CDT and RDT IBM Toronto
"Jay Alameda" ---05/24/2011 01:42:16 PM---Chris, Dave,
Chris, Dave,
I’m not so sure about this – for a makefile build, I always chose “other toolchain”, as I’ve found that the environment is managed out-of-band from Eclipse – eg, see the screenshot of the setup for remote tools – this is from Eclipse 3.6.2 – and its corresponding PTP version.
Jay
From: ptp-dev-bounces@xxxxxxxxxxx [mailto:ptp-dev-bounces@xxxxxxxxxxx] On Behalf Of Chris Recoskie Sent: Tuesday, May 24, 2011 12:31 PM To: Parallel Tools Platform general developers Subject: Re: [ptp-dev] Problem with Linux remote build from Windows 7 client
Which toolchain did you select when creating the project? If you don't pick one of the remote toolchains, then you will have this problem.
=========================== Chris Recoskie Team Lead, IBM CDT and RDT IBM Toronto
Dave Wootton ---05/24/2011 11:15:41 AM---I attempted a remote build using Indigo RC1 and the 5/23 PTP build with a remote tools connection f
I attempted a remote build using Indigo RC1 and the 5/23 PTP build with a remote tools connection from a Windows 7 client to a Linux system. I have a remote makefile project cretaed with a makefile and a single source file.
When I attempt tto build, it seenms that my Windows 7 environment is being passed to the Linux. The start of the console log looks like the following
/bin/sh: -c: line 0: syntax error near unexpected token `(' /bin/sh: -c: line 0: `echo "PID=$$ PIID=23" > /dev/pts/5; export "LOCALAPPDATA=C:\Users\dave\AppData\Local"; export "PROCESSOR_ARCHITECTURE=AMD64"; export "SESSIONNAME=Console"; export "HOMEPATH=\Users\dave"; export "LOGONSERVER=\\BIGCAT"; export
Is there a setting I'm missing to prevent my local environment from being copied to the Linux node? Dave_______________________________________________ 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
_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-dev
-- ORNL/UT Center for Molecular Biophysics cmb.ornl.gov 865-241-1537, ORNL PO BOX 2008 MS6309
-- ORNL/UT Center for Molecular Biophysics cmb.ornl.gov 865-241-1537, ORNL PO BOX 2008 MS6309
|