$ ant foobar
Buildfile: C:\work\trunk\build.xml
foobar:
[echo] PATH:
C:\cygwin64\usr\local\bin;C:\cygwin64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program
Files\TortoiseSVN\bin;C:\Program Files\Java\jdk1.7.0_51\bin;C:\Program
Files\apache-ant-1.9.3\bin;C:\Program Files (x86)\Python34;C:\Program Files
(x86)\Python34\Scripts
[echo] path: ${env.path}
[echo] Path: ${env.Path}
BUILD SUCCESSFUL
Total time: 1 second
user1@dev-pc /cygdrive/c/work/trunk
$ python3.2 --version
Python 3.4.2
On Fri, Nov 7, 2014 at 11:23 PM, Shawn Heisey <[email protected]> wrote:
> On 11/7/2014 10:16 AM, Anurag Sharma wrote:
> > I am still getting below error when running smoke on the trunk
> >
>
> <snip>
>
> > BUILD FAILED
> > C:\work\trunk\build.xml:392: Execute failed: java.io.IOException:
> > Cannot run program "python3.2": CreateProcess error=2, The system
> > cannot find the file specified
>
> <snip>
>
> > ---The file still exists
> > $ where python3.2
> > C:\Program Files (x86)\Python34\python3.2.exe
>
> That sounds like the PATH that is getting used may not include the
> location of that executable.
>
> Can you temporarily add this to the build.xml and then run "ant foobar"
> so your path variable gets output?
>
> <target name="foobar" description="Echo the path for visibility">
> <property environment="env"/>
> <echo message="PATH: ${env.PATH}" />
> <echo message="path: ${env.path}" />
> <echo message="Path: ${env.Path}" />
> </target>
>
> If the environment variable is correct in that output, then I have no
> idea what might be wrong. If you open a command prompt and type
> "python3.2 --version" ... does it work and give you the version?
>
> Thanks,
> Shawn
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
