Re: aap calling cvs problem on Windows

Thanks for the tips, Bram.

Bram Moolenaar wrote:
>
>>>This is an omission in Aap: quotes should be put around the command to
>>>include the space.  Please try the patch below.
>>
>>Seems like it ought to fix it, but it doesn't.  It results in the same 
>>error.  I also tried transposing " and ' in the relevant lines with no 
>>change in behavior.
> 
> 
> Strange, it did work for me.  Can you show me the command as it was
> executed?  The lines you show below indicate that the double quotes are
> around the cvs command, as intented.  That _should_ work...

I'll poke at it some more to see if I'm doing something else wrong.

>>So, I've temporarily worked around the problem by installing a fresh aap 
>>into C:\Programs\aap\Exec, which can now find cvs.exe.  However, I think 
>>I'm running into another weird Windows issue:
>>
>>Aap: 6 - Using dependency "build : ../src/Numerical"
>>Aap: 7 - updating target "..\src\Numerical"
>>Aap: CVS checkout for node "..\src\Numerical"
>>Aap: "C:\Programs\aap\Exec\bin\cvs.EXE" 
>>-d:pserver:[email protected]
>>:/cvsroot/numpy checkout "Numerical"
>>The filename, directory name, or volume label syntax is incorrect.
>>Aap: 7 - Do not know how to build "..\src\Numerical"
>>Aap: 7 - updating target "src\Numerical"
>>Aap: 7 - Do not know how to build "src\Numerical"
>>Aap: Do not know how to build "..\src\Numerical"
>>
>>When I run the exact command AAP claims to be running, the checkout 
>>works fine, including the double quotes on the command and module name.
> 
> 
> This probably means Aap is in the wrong directory when executing this
> command.  Unfortunately, there is no way to see the current directory.
> Except for adding a line in the Aap code:

I'll give this a try today, and see if I can figure out what's happening.

>>Is there a way to get AAP to actually tell me what it is running, or is 
>>there something in Python outside of AAP that is escaping/quoting or 
>>otherwise mangling the command that AAP has no control over?
> 
> 
> Executing system commands on MS-Windows is messy.  Best way to solve it
> is installing Linux :-).

Believe me, Windows isn't my choice--I'm doing a cross-platform build of 
  a large suite of tools.  AAP has the job of making all of this stuff a 
"one-command" build on Windows, Mac OS X, and two or more variants of 
Linux.  Windows just happens to be the platform I'm least comfortable 
on, so things confuse me more easily.  Market reality right now is that 
software customers (even those with big Linux-based clusters), often 
have a mix of desktop systems, and they want to run it on everything.

> If you are using a Unix shell that might complicate things.  Especially
> Cygwin tends to cause trouble, because it mixes up Unix and MS-Windows
> environments.  Perhaps the version of Python you installed matters for
> how system() is executed.

Cygwin is explicitly prohibited from this build process, as we already 
have enough dependencies, though Mingw32 is used to build the Fortran 
stuff and some of the stuff that won't build with msvc.  I'm suffering 
every minute I spend in cmd.exe, but it's a necessity.  ;-)

The Python is a native MSVC build of 2.3.3 as distributed from 
Python.org.  I'm actually now using my own build of it, but it is 
unmodified from the Python.org build.  I'll try reverting to the stock 
Python 2.3.3 and see if things behave differently.  (I'm certain that 
the first time I ran into, and tried the CVS quotes patch it was under 
stock 2.3.3, as I hadn't yet successfully built my own installer, so it 
was not self-hosted.)
-- 
Joe Cooper <joe-LwIbMBl5f621Z/[email protected]>
Web caching appliances and support.
http://www.swelltech.com


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click