Yes, and did the same for me with the rename command
On Oct 1, 2014 2:51 PM, "Rick McGuire" wrote:
> This article might be useful. Perhaps this is a problem with how you have
> sshd configured...it might not have permission to access that directory.
>
> Rick
>
> On Wed, Oct 1, 2014 at 9:31 AM, D
is a bit strange environment that tries to emulate a unix system. It would
be that it has its own cd command that expects unix file name conventions.
This is just a guess. cygwin always makes me nervous because it tries to
live in both worlds and does neither well.
Caused me major pain i
This article might be useful. Perhaps this is a problem with how you have
sshd configured...it might not have permission to access that directory.
Rick
On Wed, Oct 1, 2014 at 9:31 AM, David Ashley
wrote:
> Rick -
>
> This is a strange one. When I run my script(s) that perform the cmake
> build
I think this might be something to ask on the cmake list. I need a few
more specifics. When you run this in the foreground, how are you accessing
the system? Are you still going via ssh? What is your background access
mechanism?
Rick
On Wed, Oct 1, 2014 at 9:31 AM, David Ashley
wrote:
> Ric
is a bit strange environment that tries to emulate a unix system. It would
be that it has its own cd command that expects unix file name conventions.
This is just a guess. cygwin always makes me nervous because it tries to
live in both worlds and does neither well.
Rick
On Wed, Oct 1, 2014 at 9
Rick -
This is a strange one. When I run my script(s) that perform the cmake
build in the foreground I have no problems. But when I run them through
an ssh session I get an error from CMake almost right away. Right after
it discovers the Windows compiler it tries to CD to \cygwin\home\dashley
\cma
