Re: Default directory is "C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\"?

2006-04-27 Thread Danilo Turina
Not entirely true, Larry.  If he *were* to remove that installation of 
MKS, he would then discover that his Rational Rose/Clearcase/Clearquest 
installation was broken.  IBM's Rational toolkit relies on having those 
MKS tools available (and no, they cannot be coerced into using cygwin's 
tools instead).


I don't use Clearquest, but I use both Rose and ClearCase and I didn't 
installed at all MKS.


Anyway I had the problem described by the original poster when I 
installed Rational Rose the first time because I choose to install 
"Quality Architect" (if I remember well), removing that component I 
haven't had no more problems with Cygwin.


Ciao,

Danilo


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: Default directory is "C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\"?

2006-04-26 Thread Philip H. Schlesinger
Hi all.  I moved the following from my Environment Variables to a batch 
file, and now it works!  Thanks! - Phil


set TERMINFO=C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\usr\lib\terminfo
set TERMCAP=C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\etc\termcap
set TERM=nutc
set SHELL=C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\sh.exe



Larry Hall (Cygwin X) wrote:

On 04/25/2006, Charles Wilson wrote:

Larry Hall (Cygwin X) wrote:

> Without the benefit of all the info that 


> recommends, I can hazard a guess that you have a copy of the MKS tools
> installed.  These tools will conflict with the like named tools in 
Cygwin.
> Your best bet is to remove them.  You'll likely find little 
advantage to
> having them both and you certainly invite difficulties if you decide 
to keep

> them both.

Not entirely true, Larry.  If he *were* to remove that installation of 
MKS, he would then discover that his Rational 
Rose/Clearcase/Clearquest installation was broken.  IBM's Rational 
toolkit relies on having those MKS tools available (and no, they 
cannot be coerced into using cygwin's tools instead). 


Sorry Chuck and Philip.  There was no way for me to devine this possibility
from information given.  If you're right, then it may be worth the work of
separating them both and using them that way.




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: Default directory is "C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\"?

2006-04-25 Thread Larry Hall (Cygwin X)

On 04/25/2006, Charles Wilson wrote:

Larry Hall (Cygwin X) wrote:

> Without the benefit of all the info that 
> recommends, I can hazard a guess that you have a copy of the MKS tools
> installed.  These tools will conflict with the like named tools in Cygwin.
> Your best bet is to remove them.  You'll likely find little advantage to
> having them both and you certainly invite difficulties if you decide to 
keep
> them both. 



Not entirely true, Larry.  If he *were* to remove that installation of MKS, 
he would then discover that his Rational Rose/Clearcase/Clearquest 
installation was broken.  IBM's Rational toolkit relies on having those MKS 
tools available (and no, they cannot be coerced into using cygwin's tools 
instead). 


Sorry Chuck and Philip.  There was no way for me to devine this possibility
from information given.  If you're right, then it may be worth the work of
separating them both and using them that way.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: Default directory is "C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\"?

2006-04-24 Thread Charles Wilson

Larry Hall (Cygwin X) wrote:


Without the benefit of all the info that 
recommends, I can hazard a guess that you have a copy of the MKS tools
installed.  These tools will conflict with the like named tools in Cygwin.
Your best bet is to remove them.  You'll likely find little advantage to
having them both and you certainly invite difficulties if you decide to 
keep
them both. 



Not entirely true, Larry.  If he *were* to remove that installation of 
MKS, he would then discover that his Rational Rose/Clearcase/Clearquest 
installation was broken.  IBM's Rational toolkit relies on having those 
MKS tools available (and no, they cannot be coerced into using cygwin's 
tools instead).


(It's the automation stuff behind the scenes which requires MKS, not the 
cmdline 'cleartool' app; you can still call the cmd line 'cleartool' 
executable from cygwin if you want, without conflicting with MKS)


 If you want both installed, you must make sure that one

environment doesn't see the other.  That includes manipulating your PATH
appropriately and all your other shell variables.  In particular, you've
already found that MKS has set SHELL to point to it's version.  


Yep, that's the key.  I simply set my cygwin dotfiles to override those 
nasty Rational variable values.

  PATH
  TERM
  SHELL
  TERMINFO
will do it.  (you can include the dir in which cleartool.exe lives in 
your cygwin PATH; that's a different dir than the MKS junk).


You'll

likely
see other problems like this as well.  As I said, the easiest thing to 
do is
to uninstall MKS and rely on the Cygwin version of these tools for your 
needs.


Unless, of course, he actually wants to be able to USE the 
Clearcase/Clearquest/Rose tools AT ALL.  Which is likely, as he's got 
them installed.



Obviously, you are free not to take this advice but your configuration will
generally be considered non-standard by those who frequent the Cygwin 
lists so
further problems you may have as a result your MKS installation is 
likely to

fall on deaf ears. ;-)



Or, he could get it working and assist Corinna in testing the latest 
snapshot...



- Reintroducing the dirent member d_ino.  1.5.20 tries hard to return a
  useful d_ino value, which is supposed to be also the same as st_ino as
  returned by stat(2) in all cases, regardless of the obstacles to do
  this on Windows.  Do you have strange file systems like HPFS or 


 ClearCase?

--
Chuck





--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: Default directory is "C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\"?

2006-04-24 Thread Larry Hall (Cygwin X)

Schlesinger, Philip wrote:

Hi all.  I just downloaded and installed Cygwin onto a Windows 2000
Server computer.  I chose to do "All: Install".  After all was said and
done, I started the Xserver, then ran Xterm via the Start Menu (as it
didn't pop up on its own).

I got a Xterm window for about 30 seconds with the following line:

xterm: Could not exec
C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\sh.exe: No such file or
directory

I copied sh.exe to the directory it wanted.  Now I get the following
error when I open an xterm:

 70 [main] sh 1676 child_copy: stack write copy failed,
0x22E4D0..0x23, done 0, windows pid 2286596, Win32 error 5
-C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\sh: fork: No error
$ 


Since I made my install directory C:\cygwin, why the heck is it now
looking in someplace I never go to?  How do I fix this?

Help!!!



When looking for help on the Cygwin lists, it's always best to read and follow
the problem reporting guidelines found here:


Problem reports:   http://cygwin.com/problems.html


This instructs you on all the basic information a problem report should
contain, which keeps the responders to your pleas from having to ask for it
prior to helping you find your problems.

Without the benefit of all the info that 
recommends, I can hazard a guess that you have a copy of the MKS tools
installed.  These tools will conflict with the like named tools in Cygwin.
Your best bet is to remove them.  You'll likely find little advantage to
having them both and you certainly invite difficulties if you decide to keep
them both.  If you want both installed, you must make sure that one
environment doesn't see the other.  That includes manipulating your PATH
appropriately and all your other shell variables.  In particular, you've
already found that MKS has set SHELL to point to it's version.  You'll likely
see other problems like this as well.  As I said, the easiest thing to do is
to uninstall MKS and rely on the Cygwin version of these tools for your needs.
Obviously, you are free not to take this advice but your configuration will
generally be considered non-standard by those who frequent the Cygwin lists so
further problems you may have as a result your MKS installation is likely to
fall on deaf ears. ;-)

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Default directory is "C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\"?

2006-04-24 Thread Schlesinger, Philip
Hi all.  I just downloaded and installed Cygwin onto a Windows 2000
Server computer.  I chose to do "All: Install".  After all was said and
done, I started the Xserver, then ran Xterm via the Start Menu (as it
didn't pop up on its own).

I got a Xterm window for about 30 seconds with the following line:

xterm: Could not exec
C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\sh.exe: No such file or
directory

I copied sh.exe to the directory it wanted.  Now I get the following
error when I open an xterm:

 70 [main] sh 1676 child_copy: stack write copy failed,
0x22E4D0..0x23, done 0, windows pid 2286596, Win32 error 5
-C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\mksnt\sh: fork: No error
$ 

Since I made my install directory C:\cygwin, why the heck is it now
looking in someplace I never go to?  How do I fix this?

Help!!!

- Phil


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/