From: neil AT riskware DOT co DOT uk Subject: Mount - is there a limitation I'm not aware of? 28 Nov 1997 06:24:45 -0800 Message-ID: <9711280855.AA00594.cygnus.gnu-win32@_riskware.co.uk> To: gnu-win32 AT cygnus DOT com Cc: neil AT riskware DOT co DOT uk Good day all, I'm attempting to re-compile our software on NT. It has been developed under Unix in a Clearcase environment using imake. If you use Clearcase on both Unix and NT you will be aware that paths to Clearcase files in Unix begin /vobs/ while on NT is mapped to a drive letter. This means that all the paths specified in the imake files are not valid on NT. The gnu-win32 mount command undoes this damage by allowing drive letters to be mounted from / thus the G: drive which has Clearcase files could be mounted /vobs/ so that G: becomes /vobs/ ... the Unix paths are now valid on NT! Now comes the sticking point, while the above is true with the gnu-win32 provided bash shell the build (which uses the Visual C++ "cl" command to compile) still claims that the paths are invalid and I'm beginning to think that there may be some limitation to the mount command that stops "cl" from seeing the clever stuff that mount has done. Could someone explain it to me (and hopefully say it aint so? - it looked like a great fix to the path problem) ? Advice from anyone who has done a similar job using imake and/or Clearcase also welcome (the imake list is so... quiet) thanks to all, Neil J Mackie. - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".