Thanks to Larry and Gerry for the discussion that has led to a solution
for me too -- while occupied by something else or sleeping at GMT+1.
Stopping processes started by cygrunsrv and a reinstall did it.
Jørgen
On 01/31/2011 04:50 PM, Larry Hall (Cygwin) wrote:
> On 1/31/2011 4:42 PM, Gerry R
On 01/31/2011 04:50 PM, Larry Hall (Cygwin) wrote:
> On 1/31/2011 4:42 PM, Gerry Reno wrote:
>> On 01/31/2011 04:16 PM, Gerry Reno wrote:
>>> On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote:
>>>
On 1/31/2011 3:49 PM, Gerry Reno wrote:
> On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wr
On 1/31/2011 4:42 PM, Gerry Reno wrote:
On 01/31/2011 04:16 PM, Gerry Reno wrote:
On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote:
On 1/31/2011 3:49 PM, Gerry Reno wrote:
On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote:
This is why you got the complaint about cygwin1.dll being busy
On 01/31/2011 04:16 PM, Gerry Reno wrote:
> On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote:
>
>> On 1/31/2011 3:49 PM, Gerry Reno wrote:
>>
>>> On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote:
>>>
>>
>>
>>
This is why you got the complaint about cygwin1.dll being busy
On 1/31/2011 4:16 PM, Gerry Reno wrote:
On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote:
On 1/31/2011 3:49 PM, Gerry Reno wrote:
On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote:
This is why you got the complaint about cygwin1.dll being busy.
When you did the upgrade, did you download
On 01/31/2011 04:14 PM, Larry Hall (Cygwin) wrote:
> On 1/31/2011 3:49 PM, Gerry Reno wrote:
>> On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote:
>
>
>
>>>
>>> This is why you got the complaint about cygwin1.dll being busy.
>>>
>>> When you did the upgrade, did you download the current 'setup.exe
On 1/31/2011 3:49 PM, Gerry Reno wrote:
On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote:
This is why you got the complaint about cygwin1.dll being busy.
When you did the upgrade, did you download the current 'setup.exe' from
cygwin.com?
Yes.
Hm. There was an issue with 'setup.exe' n
On 01/31/2011 03:00 PM, Larry Hall (Cygwin) wrote:
> On 1/31/2011 2:16 PM, Gerry Reno wrote:
>> On 01/31/2011 01:55 PM, Gerry Reno wrote:
>>> In my case, I installed cygwin a few months ago and yesterday I went to
>>> upgrade it and install several packages.
>>>
>>> As it was going along it said th
On 1/31/2011 2:16 PM, Gerry Reno wrote:
On 01/31/2011 01:55 PM, Gerry Reno wrote:
In my case, I installed cygwin a few months ago and yesterday I went to
upgrade it and install several packages.
As it was going along it said that cygwin1.dll was busy so I pressed
Continue and at the end it said
On 01/31/2011 01:55 PM, Gerry Reno wrote:
> In my case, I installed cygwin a few months ago and yesterday I went to
> upgrade it and install several packages.
>
> As it was going along it said that cygwin1.dll was busy so I pressed
> Continue and at the end it said a reboot was required. And so I
In my case, I installed cygwin a few months ago and yesterday I went to
upgrade it and install several packages.
As it was going along it said that cygwin1.dll was busy so I pressed
Continue and at the end it said a reboot was required. And so I
rebooted the machine.
When I logged back in, cygw
On 01/31/2011 10:15 AM, Jørgen Steensgaard wrote:
> Hi
>
> I have just installed 1.7.7 after several unsuccessful attempts.
> Several auxiliary libraries were not included in the installation
> after setup finished. OK -- so I had to locate and rerun setup
> repeatedly.
>
> At some point I succeed
On 2011-01-31 15:15Z, Jørgen Steensgaard wrote:
>
> I have just installed 1.7.7 after several unsuccessful attempts. Several
> auxiliary libraries were not included in the installation after setup
> finished. OK -- so I had to locate and rerun setup repeatedly.
cygcheck output indicates versio
13 matches
Mail list logo
