Solved. What I've done was the clean install[1]. But I don't
know what did the trick nor the cause of the problem[2] after
all. Performing rebaseall doesn't seem to do any harm in this
installation.
Regards,
[1] Rename c:\cygwin\ to c:\cygwin_old\
Install Cygwin in c:\cygwin\ using setup.e
On 2013-07-18 AM 10:53, Warren Young wrote:
Nothing so simple. Locking is handled at the OS and/or Cygwin DLL
level. The build change between 3.7.16.2 and 3.7.17-3 is that we're now
relying on new features in the Cygwin DLL to do Windows-style locking by
default.
Older versions of Cygwin SQLit
On Jul 18 17:11, jojelino wrote:
> On 2013-07-18 AM 10:53, Warren Young wrote:
> >Nothing so simple. Locking is handled at the OS and/or Cygwin DLL
> >level. The build change between 3.7.16.2 and 3.7.17-3 is that we're now
> >relying on new features in the Cygwin DLL to do Windows-style locking b
On Jul 18 11:38, Roland Schwingel wrote:
> Hi...
>
> Today I updated my cygwin to version 1.7.21. Due to a bunch of
> lockup problems I was previously sticking to 1.7.17. A short test
> shows that the lockups appears to be solved (that are the good news
> - thanks to all involved) - but I got a ne
Hi Guys,
i dont know why ln is not working.
this is what i did.
C:\Users\test1>pushd
\\ostorenas\odi\ostore_platform_logs\ostore\7.4.0\test1\linux64
Z:\ostore_platform_logs\ostore\7.4.0\test1\linux64>c:\cygwin\bin\ln -s
diva_test LATEST
in the above line "diva_test" is a folder.
it is created
On Jul 18 16:15, Divakar K wrote:
> Hi Guys,
>
> i dont know why ln is not working.
>
> this is what i did.
>
> C:\Users\test1>pushd
> \\ostorenas\odi\ostore_platform_logs\ostore\7.4.0\test1\linux64
>
> Z:\ostore_platform_logs\ostore\7.4.0\test1\linux64>c:\cygwin\bin\ln -s
> diva_test LATEST
>
I have a very recent version of Cygwin and using the SIPP application. This
calls nanosleep from within a thread.
Effectively , every second, the application
* Creates a thread
* Calls nanosleep 9 times.
* Deletes the thread
And every second, according to windows task
[What an odd subject line]
On Thu, Jul 18, 2013 at 04:23:32PM +0100, trefor.2.edwa...@bt.com wrote:
>I have a very recent version of Cygwin and using the SIPP application.
>This calls nanosleep from within a thread.
"Very recent" is not a precise enough distinction for debugging
problems.
See: ht
Hi,
sorry if this isn't the correct place. I have previously used the
mingw-* packages to create a Windows compile of tcl8.6.0, but currently
it doesn't work. It compiles without error as far as I can see, but when
you try to run the executable (tclsh8.6.0.exe) it returns immediately
with cod
On 2013-07-18 PM 5:59, Corinna Vinschen wrote:> On Jul 18 17:11,
jojelino wrote:
>> On 2013-07-18 AM 10:53, Warren Young wrote:
>>> Nothing so simple. Locking is handled at the OS and/or Cygwin DLL
>>> level. The build change between 3.7.16.2 and 3.7.17-3 is that
we're now
>>> relying on new f
Hi Team,
i have installed the latest version of the CYgwin ( 1.7 ) , for the
build activities of the NT builds.
i am not able to set/unset env variables.
every time the following error pops up :
set/unset not recognized as internal or external command.
i have latest bash installed.
i am not abl
11 matches
Mail list logo