Hi,

the problem seems to be that you're using a client spec with a root in DOS/Windows notation, not in the Cygwin notation. E.g. if your root is 'c:\source' then you have to change the root in the client spec to '/source' and the command works. Sadly after changing the root in this way the SCC integration and the p4win does not work any longer. It does not help to use the p4 client for cygwin, this problem remains. To use a second client spec is not an option either, since the server naturally keeps track which files are checked out at which client, so it is not possible to use the p4win and the p4 command line in the bash in a transparent way for this two different clients.

The best solution would be the capability of the p4 cygwin client to handle the root in DOS/Windows notation as well as the cygwin notation, but this is an enhancement to be done by Perforce (Feature request: CALL#62922).

As a workaround you may provide the p4 command with the optional -d option to set the working directory in DOS/Windows notation. That would work also. Therefore I have added a function to my .bashrc to add this converstion to every Perforce command from the cygwin bash:

function py { p4 -d $(cygpath -w $PWD) $* }

With this definition you will have to call 'py have *' to get the proper results. But this is solution is very nasty if you have to setup and support a lot of development environments.

Regards, J?rg

---------------------------------------- Message History ----------------------------------------

From: MKoh...@nomadix.com on 18/01/2000 18:29

To: perforce-user at perforce.com cc: Subject: [p4] 'p4 have * ' under NT Cygwin bash