Re: Strange errors running gcc tests on Cygwin

On 03/07/2017 06:36 PM, David Billinghurst wrote: On 8/03/2017 10:25, Daniel Santos wrote: My concern is with the dynamic portion of this behavior -- what is affected by environment variables. Many years ago I ran a nightly build/test of gcc under cygwin and reported the results to gcc-testr

Re: Symlink file size

On 3/7/2017 10:37 PM, Steven Penny wrote: Cygwin seems to have no way to print an accurate size of a symlink. Consider this command: $ touch alfa.txt $ CYGWIN= ln -s alfa.txt bravo.txt Now cmd.exe can print the correct size just fine: > dir /AS 2017-03-07 09:26 PM3

Symlink file size

Cygwin seems to have no way to print an accurate size of a symlink. Consider this command: $ touch alfa.txt $ CYGWIN= ln -s alfa.txt bravo.txt Now cmd.exe can print the correct size just fine: > dir /AS 2017-03-07 09:26 PM30 bravo.txt However Cygwin prints incorrec

Re: tar 1.29 regression, duplicating files with -T and --no-recursion

> $ tar -czf test.tar.gz -T tartest/filelist.txt --no-recursion Looks like this was an intentional change: http://lists.gnu.org/archive/html/bug-tar/2016-05/msg8.html --no-recursion is apparently positional, so the fact that this worked before http://git.savannah.gnu.org/cgit/tar.git/commit/?

Re: Changing behaviour of pthread_cond_wait().

On Tue, 7 Mar 2017 15:33:06 +0100 Corinna Vinschen wrote: > I applied a patch to change the behaviour as proposed, and uploaded > new snapshots to https://cygwin.com/snapshots/ for testing. Confirmed. Thanks much. -- Takashi Yano -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Strange errors running gcc tests on Cygwin

On 8/03/2017 10:25, Daniel Santos wrote: My concern is with the dynamic portion of this behavior -- what is affected by environment variables. Many years ago I ran a nightly build/test of gcc under cygwin and reported the results to gcc-testresults. There may be is discussion on the gcc mai

tar 1.29 regression, duplicating files with -T and --no-recursion

Test case: Tony@LAPTOP-O230JCFF ~ $ tar --version tar (GNU tar) 1.29 Packaged by Cygwin (1.29-1) Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later . This is free software: you are free to change and redistribute it. Ther

Re: Strange errors running gcc tests on Cygwin

On 03/07/2017 07:58 AM, cyg Simple wrote: On 3/6/2017 9:03 PM, Daniel Santos wrote: On 03/05/2017 05:08 AM, David Billinghurst wrote: No. LD_LIBRARY_PATH is used by dlopen (). PATH is one of the locations searched by Windows when starting applications, see https://msdn.microsoft.com/en-us/lib

pthread_create() slowdown with concurrent sched_yield()

I suspect I may have discovered a corner-case performance bug in Cygwin's pthread_create() implementation. The problem arises when a call to pthread_create() is made concurrently with multiple pthreads in the same process spinning on calls to sched_yield(). I've searched the Cygwin mailing list arc

Re: Failed password for invalid user

On Mar 6 09:48, jesus san miguel wrote: > Hi Andrey, > > Thanks for your answer, but I am using password-less authentication > too (with public/private keys), so /etc/password is necessary, isn't > it? No! Who told you that? As long as you use the user account name the way it's called in Cygwi

Re: Failed password for invalid user

On Mar 3 10:03, jesus san miguel wrote: > I am running cygwin 2.7.0 sshd service under a local cyg_server account. > > I wanted to avoid case sensitive problems by duplicating users in > /etc/passwd, but I find mixed results: > I can login as "Administrator", "MYPC+Administrator" and "miabuela",

Re: Failed password for invalid user

On 3/6/2017 4:22 AM, Andrey Repin wrote: > Greetings, jesus san miguel! > >> Besides, user alias "miabuela" is working as expected. Why shouldn't >> "administrator" alias work as well? > > That's the worst idea I've heard since morning. > It's a legacy idea to allow different users control a pa

Re: Profile XXXXX failed to execute.

On 3/6/2017 6:11 AM, Nilesh Shedge wrote: > Can you please enlist the file which I need to replace? > See http://cygwin.com and download the most recent setup.exe for your platform system (32bit vs 64bit). It will know what to update. > > -- > Problem reports: http://cygwin.com/problems.

Re: Perl: Can't compile Module::Build::Tiny (required by Perl::Critic)

On Mon, Mar 6, 2017 at 11:52 AM, Achim Gratz wrote: > Most likely a new test. Testing for read-only status quite often doesn't work > as expected on Windows due to write/change access being granted by some DACL > somewhere up the directory chain (or when you are in the Administrators > group or

Re: Changing behaviour of pthread_cond_wait().

Hi, On Mar 7 20:43, Takashi Yano wrote: > Hello, > > I would like to propose chaging behaviour of pthread_cond_wait(). > > POSIX states as follows about pthread_cond_wait(): > If a signal is delivered to a thread waiting for a condition variable, > upon return from the signal handler the thread

Re: cygwin console software

Until a few months ago, I used PuttyCyg. It worked really well, and still does, and I used it for perhaps 10 years. In the past few months, I've been using Tera Term, which has a Cygwin mode that works just like MinTTY and PuttyCyg with the few differences I've noticed: 1PuttyCyg and oth

Re: Strange errors running gcc tests on Cygwin

On 3/6/2017 9:03 PM, Daniel Santos wrote: > On 03/05/2017 05:08 AM, David Billinghurst wrote: >> No. >> >> LD_LIBRARY_PATH is used by dlopen (). >> >> PATH is one of the locations searched by Windows when starting >> applications, see https://msdn.microsoft.com/en-us/library/7d83bc18.aspx > > Than

Changing behaviour of pthread_cond_wait().

Hello, I would like to propose chaging behaviour of pthread_cond_wait(). POSIX states as follows about pthread_cond_wait(): If a signal is delivered to a thread waiting for a condition variable, upon return from the signal handler the thread resumes waiting for the condition variable as if it was