On Tue, 2003-07-29 at 20:22, Max Bowsher wrote:
> Rob Clack wrote:
> > Thank you for this. However, I managed to find a disaster in there
> > despite everything. :o(
> >
> > I renamed the whole e:\cygwin tree to e:\old_cygwin. I had to rerun the
> > install several times, for reasons I need not
Rob Clack wrote:
> Thank you for this. However, I managed to find a disaster in there
> despite everything. :o(
>
> I renamed the whole e:\cygwin tree to e:\old_cygwin. I had to rerun the
> install several times, for reasons I need not go into. Eventually it
> got to the end and said "I found a
Thank you for this. However, I managed to find a disaster in there
despite everything. :o(
I renamed the whole e:\cygwin tree to e:\old_cygwin. I had to rerun the
install several times, for reasons I need not go into. Eventually it
got to the end and said "I found an old cygwin, shall I del
Igor Pechtchanski wrote:
On Fri, 25 Jul 2003, Rob Clack wrote:
Can I just rename my old cygwin directory tree (E:\cygwin) to something
else and install the latest in its place? I did read somewhere that you
shouldn't have two cygwin1.dlls, hence the question.
Thanks in advance
Rob
Yes, you
On Fri, 25 Jul 2003, Igor Pechtchanski wrote:
> [snip]
> If you want to be completely safe, rename the old cygwin1.dll to, say,
> old-cygwin1.dll (I have a few on my system, no problems yet).
^
Just to be completely clear (for the archives), I have a few
On Fri, 25 Jul 2003, Rob Clack wrote:
> We have a large c/unix application which uses gtk and which has been
> ported to Windows. Our gtk is ancient, as is our cygwin, and we're
> looking to upgrade both.
>
> The cygwin was, I gather, seriously hacked (some time ago) to get it to
> work, and I do
6 matches
Mail list logo
