I agree with both of you. It is definitely a path
problem, and i also agree that the cygwin bin
shouldn't be in the windows path and vice versa.
However, from the number of bug reports that i have
received from wingaim users, it seems that it is a
common practice to put the cygwin bin directory
Daniel Atallah wrote:
I agree with both of you. It is definitely a path
problem, and i also agree that the cygwin bin
shouldn't be in the windows path and vice versa.
Well, we also use Cygwin tools from a lot of non-cygwin programs (e.g.
Visual C++), so it has to be in the Windows Path, at
At 07:36 PM 2/4/2004, Shankar Unni you wrote:
Daniel Atallah wrote:
I agree with both of you. It is definitely a path
problem, and i also agree that the cygwin bin
shouldn't be in the windows path and vice versa.
Well, we also use Cygwin tools from a lot of non-cygwin programs (e.g. Visual
I have upgraded to cygwin 1.5.7 and can no longer execute wincvs in a cygwin
bash shell.
After I execute the command: wincvs
The wincvs windows start to appear then it just exits.
$ echo $?
128
-Stephen More
NOTICE: This e-mail may contain confidential or legally privileged
maintain the
cygwin tcl, so i have posted this message to their
list as well.
-D
--- [EMAIL PROTECTED] wrote:
I have upgraded to cygwin 1.5.7 and can no longer
execute wincvs in a cygwin
bash shell.
After I execute the command: wincvs
The wincvs windows start to appear then it just
exits
: wincvs and cygwin
I believe that this is related to the problem that i
have with gaim.
If the tcl dll included with cygwin conflicts with the
native win32 tcl (still a problem if you don't have
native tcl installed)
When wincvs tries to start up, it probes for a tcl
dll, and when it finds
Daniel Atallah wrote:
If the tcl dll included with cygwin conflicts with the
native win32 tcl (still a problem if you don't have
native tcl installed)
Yes - I don't think this is a conflict per se, rather than simply
finding and trying to load the cygwin tcl84.dll.
Have there been any
On Tue, 3 Feb 2004, Shankar Unni wrote:
Daniel Atallah wrote:
If the tcl dll included with cygwin conflicts with the
native win32 tcl (still a problem if you don't have
native tcl installed)
Yes - I don't think this is a conflict per se, rather than simply
finding and trying to load
The problem lies in that anything that is linked
against the native dll will not work with the cygwin
dll. The problem is simple, the program will use the
first matching dll that it finds in the search path.
It isn't a wincvs (or gaim in my case) problem, there
is nothing that they can really do
my 2 cents, and what i believe is an easier and more appropriate
solution ( think like you're on unix/linux) - for your cygwin
bash/rxvt/etc terminals explicitely set the path in your .bashrc such
that the cygwin binaries are found first -- and either do not add the
cygwin binary paths to the
On Tue, 3 Feb 2004, Reid Thompson wrote:
my 2 cents, and what i believe is an easier and more appropriate
solution ( think like you're on unix/linux) - for your cygwin
bash/rxvt/etc terminals explicitely set the path in your .bashrc such
that the cygwin binaries are found first -- and either
2002 20:25
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Warning: Latest version of Cygwin DLL makes WinCVS (through
Cygwin SSH) not work (Intern)
For anyone reading this, please see the email archives for the same
proclamation by others and the recommended solution. The results
]
Subject: Warning: Latest version of Cygwin DLL makes WinCVS (through Cygwin
SSH) not work (Intern)
Hi!
I upgraded Cygwin yesterday (Cygwin DLL 1.3.13-2?). When I used WinCVS
today through Cygwin OpenSSH I got an error message when updating a file
saying 'OK unknown response'. After downgrading
Hi!
I upgraded Cygwin yesterday (Cygwin DLL 1.3.13-2?). When I used WinCVS today through
Cygwin OpenSSH I got an error message when updating a file saying 'OK unknown
response'. After downgrading to 1.3.12-4 this error disappeared.
We had a similar problem with a previous version of Cygwin DLL
14 matches
Mail list logo
