Re: Cygwin build from source is broken since binutils-2.42-1

On Feb 12 11:10, Christian Franke via Cygwin wrote: > This is not a binutils regression: A build from cygwin 3.5.0-1 src package > or current newlib-cygwin git main (bfb68a9) with new binutils-2.42-1 fails > with: > > " > In file included from ../../../../winsup/utils/dumper.cc:23: > /usr/include/

Cygwin build from source is broken since binutils-2.42-1

This is not a binutils regression: A build from cygwin 3.5.0-1 src package or current newlib-cygwin git main (bfb68a9) with new binutils-2.42-1 fails with: " In file included from ../../../../winsup/utils/dumper.cc:23: /usr/include/bfd.h:2748:1: error: expected initializer before ‘ATTRIBUTE_WA

Re: CMake support into libssh-0.8.7-1 is broken.

Hello, Il giorno gio 20 gen 2022 alle ore 20:07 Marco Atzeri ha scritto: > > On 15.01.2022 14:19, Marco Atzeri wrote: > > On 14.01.2022 23:30, Carlo B. wrote: > >> Hello, > >> I discovered that CMake support into current libssh-0.8.7-1 is broken. > >> Afte

Re: CMake support into libssh-0.8.7-1 is broken.

On 15.01.2022 14:19, Marco Atzeri wrote: On 14.01.2022 23:30, Carlo B. wrote: Hello, I discovered that CMake support into current libssh-0.8.7-1 is broken. After you installed the development package, you just need to add this line into a dummy CMakeLists.txt: find_package(libssh) So, I

CMake support into expat-2.4.1 is broken.

Hello, I tried to build the latest stable of OpenColorIO but I got an error because the support for CMake into expat is broken. I'm getting this message: CMake Error at /usr/lib/cmake/expat-2.4.1/expat.cmake:74 (message): The imported target "expat::expat" references the file

Re: CMake support into libssh-0.8.7-1 is broken.

On 14.01.2022 23:30, Carlo B. wrote: Hello, I discovered that CMake support into current libssh-0.8.7-1 is broken. After you installed the development package, you just need to add this line into a dummy CMakeLists.txt: find_package(libssh) and into the console you will read: CMake Error

CMake support into libssh-0.8.7-1 is broken.

Hello, I discovered that CMake support into current libssh-0.8.7-1 is broken. After you installed the development package, you just need to add this line into a dummy CMakeLists.txt: find_package(libssh) and into the console you will read: CMake Error at /usr/lib/cmake/libssh/libssh

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

Yes, this commit solved the issue! And cygwin1-20210707.dll.xz works fine! Thank you very much! чт, 8 июл. 2021 г. в 17:13, Takashi Yano : > On Thu, 8 Jul 2021 16:35:41 +0600 > Егоров Егор via Cygwin wrote: > > Hello! > > May be bisect result help: > > > > e_egorov@inp-w-egorov-e /tmp/newlib-cyg

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

On Thu, 8 Jul 2021 20:12:36 +0900 Takashi Yano wrote: > Does your issue also happen after the following commit? > > commit 98e3aeb1f521151f5b18fc2af9a8fecf11a98e76 > Author: Takashi Yano > Date: Thu Jun 24 12:40:58 2021 +0900 Please note that not 1b242c12 but 98e3aeb1. -- Takashi Yano --

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

On Thu, 8 Jul 2021 16:35:41 +0600 Егоров Егор via Cygwin wrote: > Hello! > May be bisect result help: > > e_egorov@inp-w-egorov-e /tmp/newlib-cygwin > $ git bisect bad > ff4440fcf7687d9af05f4c2fcb163fca5b2167f9 is the first bad commit > commit ff4440fcf7687d9af05f4c2fcb163fca5b2167f9 > Author: Ta

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

insertions(+), 2 deletions(-) чт, 8 июл. 2021 г. в 01:05, Andrey Repin : > Greetings, Егоров Егор! > > > I have a similar problem too. > > Unfortunately, "me too" is not a useful issue report. > > > After upgrading to cygwin-3.2.0 the input of Cyrillic characters i

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

Greetings, Егоров Егор! > I have a similar problem too. Unfortunately, "me too" is not a useful issue report. > After upgrading to cygwin-3.2.0 the input of Cyrillic characters in the > bash console is broken. Can we expect a fix for the problem in the next > nightly

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

Hello! I have a similar problem too. After upgrading to cygwin-3.2.0 the input of Cyrillic characters in the bash console is broken. Can we expect a fix for the problem in the next nightly builds? Thank you. -- Regards, Egor Y. Egorov -- Problem reports: https://cygwin.com/problems.html

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

On Wed, 23 Jun 2021 11:07:44 +0500 Eugene Klimov wrote: > Thanks a lot, in cygwin 3.1.7 error not present Thanks. Hmm, I may have found the culprit. I will submit a patch which possibly fixes the issue. -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ:

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

Thanks a lot, in cygwin 3.1.7 error not present ср, 23 июн. 2021 г. в 08:09, Takashi Yano : > > On Tue, 22 Jun 2021 18:34:03 +0500 > Eugene Klimov wrote: > > > LANG=en_US.UTF-8 > > LC_CTYPE="en_US.UTF-8" > > LC_NUMERIC="en_US.UTF-8" > > LC_TIME="en_US.UTF-8" > > LC_COLLATE="en_US.UTF-8" > > LC_MON

Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

On Tue, 22 Jun 2021 18:34:03 +0500 Eugene Klimov wrote: > LANG=en_US.UTF-8 > LC_CTYPE="en_US.UTF-8" > LC_NUMERIC="en_US.UTF-8" > LC_TIME="en_US.UTF-8" > LC_COLLATE="en_US.UTF-8" > LC_MONETARY="en_US.UTF-8" > LC_MESSAGES="en_US.UTF-8" > LC_ALL=en_US.UTF-8 > TERM=xterm-256color > > when i run cygwi

cygwin-3.2.0 + windows 10 - russian cyrilic input is broken

LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_ALL=en_US.UTF-8 TERM=xterm-256color when i run cygwin.bat from any cmd.exe or just run bash.exe and try to input cyrillic character

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On Tue, Jan 12, 2021 at 5:20 PM Andrey Repin wrote: > > Again, the properties are read BY SYSTEM at the moment the link is created. > In other words, Windows is unable to create a link to nonexistent > (unreachable) target (not directly, at least). This is false. Links can be created arbitrarily

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

Greetings, Matt D.! Please no top posting in this list. > On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin wrote: >> >> On 1/4/2021 10:27 AM, Matt D. via Cygwin wrote: >> > I am using symbolic links native to Windows. My CYGWIN environment >> > variable has been set to "winsymlinks:nativ

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

Operations like cp and rsync etc. should still work. The type of symbolic link to be created can be read from the file attributes of the one being copied. On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin wrote: > > On 1/4/2021 10:27 AM, Matt D. via Cygwin (cygwin@cygwin.com) wrote: > >

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

Matt D. via Cygwin writes: > The normal behavior for both Windows and Linux is to create the > symbolic link whether the target exists or not. That's not the case on Windows or rather it has restrictions that can trip you up. On Windows you must specify if the symbolic link points to a directory

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On 1/4/2021 10:27 AM, Matt D. via Cygwin wrote: > I think there is a misunderstanding with how to set up your > environment to reproduce my test cases. I did state in the subject > "native symbolic links" but I can see that this can be misinterpreted > and I should have clarified. > > I am using s

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On 1/4/2021 10:27 AM, Matt D. via Cygwin (cygwin@cygwin.com) wrote: > I am using symbolic links native to Windows. My CYGWIN environment > variable has been set to "winsymlinks:nativestrict" and my account has > permission to make symbolic links. This is an issue specifically with > Cygwin; I have

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

I think there is a misunderstanding with how to set up your environment to reproduce my test cases. I did state in the subject "native symbolic links" but I can see that this can be misinterpreted and I should have clarified. I am using symbolic links native to Windows. My CYGWIN environment varia

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On 1/4/2021 5:36 AM, Matt D. via Cygwin wrote: > Did you try any of my test cases? This can't and doesn't work for the > reasons I outlined in my previous message: > > $ cp -av folder_a/a folder_b/ > 'folder_a/a' -> 'folder_b/a' > cp: cannot create symbolic link 'folder_b/a': No such file or direc

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

Did you try any of my test cases? This can't and doesn't work for the reasons I outlined in my previous message: $ cp -av folder_a/a folder_b/ 'folder_a/a' -> 'folder_b/a' cp: cannot create symbolic link 'folder_b/a': No such file or directory $ cp -dv folder_a/a folder_b/ 'folder_a/a' -> 'folder

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On 2021-01-02 21:16, Matt D. via Cygwin wrote: I have a folder with a lot of native Windows symbolic links. I want to copy this folder. I cannot rsync or cp this folder due to Cygwin being unable to create symbolic links without also wanting to verify the link target. This can be demonstrated:

Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

I have a folder with a lot of native Windows symbolic links. I want to copy this folder. I cannot rsync or cp this folder due to Cygwin being unable to create symbolic links without also wanting to verify the link target. This can be demonstrated: $ ln -s a b ln: failed to create symbolic link 'b

Re: Back history is broken for sqlite3 3.27.2-1

Thanks! Since I just need the shell. For now I'll just rollback to the previous version instead. On Tue, Apr 23, 2019 at 2:00 AM Jan Nijtmans wrote: > Op ma 22 apr. 2019 12:32 schreef 斟酌鵬兄: > > > Hi, > > > > Not sure if I have to report it here. Otherwise please direct me to the > > correct plac

Re: Back history is broken for sqlite3 3.27.2-1

Op ma 22 apr. 2019 12:32 schreef 斟酌鵬兄: > Hi, > > Not sure if I have to report it here. Otherwise please direct me to the > correct place for filing reports. > > This version does not support the Up-Arrow key for previously entered > commands. > > The last working version is 3.21.0-1 > Yes, this i

Back history is broken for sqlite3 3.27.2-1

Hi, Not sure if I have to report it here. Otherwise please direct me to the correct place for filing reports. This version does not support the Up-Arrow key for previously entered commands. The last working version is 3.21.0-1. -- Regards, Penguin -- Problem reports: http://cygwin.com/p

Re: [BUG] Package mingw64-x86_64-icu is broken

On 06/19/2018 10:18 AM, Stefan Weil wrote: > Am 19.06.2018 um 11:53 schrieb JonY: >> On 06/18/2018 12:12 PM, Stefan Weil wrote: >>> Am 06.06.2018 um 21:13 schrieb Stefan Weil: Both mingw64-x86_64-icu-57.1-1 and mingw64-x86_64-icu-57.1-2 are broken: This code always fails: i

Re: [BUG] Package mingw64-x86_64-icu is broken

Am 19.06.2018 um 11:53 schrieb JonY: > On 06/18/2018 12:12 PM, Stefan Weil wrote: >> Am 06.06.2018 um 21:13 schrieb Stefan Weil: >>> Both mingw64-x86_64-icu-57.1-1 and mingw64-x86_64-icu-57.1-2 are broken: >>> >>> This code always fails: >>> >>> icu::Normalizer2::getInstance(nullptr, "nfkc", UNORM2

Re: [BUG] Package mingw64-x86_64-icu is broken

On 06/18/2018 12:12 PM, Stefan Weil wrote: > Am 06.06.2018 um 21:13 schrieb Stefan Weil: >> Both mingw64-x86_64-icu-57.1-1 and mingw64-x86_64-icu-57.1-2 are broken: >> >> This code always fails: >> >> icu::Normalizer2::getInstance(nullptr, "nfkc", UNORM2_COMPOSE, error_code); >> >> The problem was

Re: [BUG] Package mingw64-x86_64-icu is broken

Am 06.06.2018 um 21:13 schrieb Stefan Weil: > Both mingw64-x86_64-icu-57.1-1 and mingw64-x86_64-icu-57.1-2 are broken: > > This code always fails: > > icu::Normalizer2::getInstance(nullptr, "nfkc", UNORM2_COMPOSE, error_code); > > The problem was detected when comparing Tesseract for Windows > e

[BUG] Package mingw64-x86_64-icu is broken

Both mingw64-x86_64-icu-57.1-1 and mingw64-x86_64-icu-57.1-2 are broken: This code always fails: icu::Normalizer2::getInstance(nullptr, "nfkc", UNORM2_COMPOSE, error_code); The problem was detected when comparing Tesseract for Windows executables: while the 32 bit version worked fine, the 64 bit

file-5.30 is broken, please update to file-5.32

file 5.32 was released on Sep. 1, 2017 https://github.com/file/file/tree/FILE5_32 ftp://ftp.astron.com/pub/file/ It addresses a number of ongoing issues, including an off-by-one that breaks the search command in magic files. Thanks for your conside

Re: Cygwin install is broken v-a-vis dependencies

On 04/04/2017 14:45, Henry S. Thompson wrote: cyg Simple writes: On 4/3/2017 8:01 PM, Marco Atzeri wrote: As Dan explained the default behavior of cygwin setup is to update already installed packages and their dependencies. Maybe so but even I find that this is cumbersome. I would prefer a

Re: Cygwin install is broken v-a-vis dependencies

cyg Simple writes: > On 4/3/2017 8:01 PM, Marco Atzeri wrote: >> >> As Dan explained the default behavior of cygwin setup is to update >> already installed packages and their dependencies. > > Maybe so but even I find that this is cumbersome. I would prefer a > choice upfront just after the downl

Re: Cygwin install is broken v-a-vis dependencies

On 4/3/2017 8:01 PM, Marco Atzeri wrote: > On 03/04/2017 23:54, Dan Kegel wrote: > > Dan, > No TOP post here please > >> That probably just means there have been updates since >> last time you installed, and it's trying to update things >> you installed before (or that get installed by default).

Re: Cygwin install is broken v-a-vis dependencies

On 03/04/2017 23:54, Dan Kegel wrote: Dan, No TOP post here please That probably just means there have been updates since last time you installed, and it's trying to update things you installed before (or that get installed by default). Try running setup, don't change anything, and let it fini

Re: Cygwin install is broken v-a-vis dependencies

That probably just means there have been updates since last time you installed, and it's trying to update things you installed before (or that get installed by default). Try running setup, don't change anything, and let it finish. That will grab all the updates you need. After that, it'll behave

Cygwin install is broken v-a-vis dependencies

Whenever I go to install a package, I get a list of 50 other packages that it claims need to be installed. I know that list is both bogus and contains items I explicitly need to not oinstall (e.g. cmake). What is worse, when I want to uninstall a package, it gives me that ]same list plus it wants

Re: python-gdal is broken by libproj9 4.9.3-1 update

On 08/11/2016 00:13, Chris wrote: Hello, in python-gdal 2.1.1-1 _gdal.dll still uses cygproj-9.dll, but it was replaced with cygproj-12.dll in libproj9 4.9.3-1 so the import fails. I was able to get a working system by downgrading libproj9 to 4.9.2-1 and libgeotiff2 to 1.4.1-1. -- Hi Chris,

python-gdal is broken by libproj9 4.9.3-1 update

Hello, in python-gdal 2.1.1-1 _gdal.dll still uses cygproj-9.dll, but it was replaced with cygproj-12.dll in libproj9 4.9.3-1 so the import fails.   I was able to get a working system by downgrading libproj9 to 4.9.2-1 and libgeotiff2 to 1.4.1-1. -- Problem reports: http://cygwin.com/probl

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Corinna, On Mon, 23 Mar 2015 11:08:23 +0100 Corinna Vinschen wrote: > With this out of the way, I'm just looking through your patch and it > looks good to me. I have only a few minor style nits: > > + rc ++; > > No space between the variable and the increment operator,

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Takashi, On Mar 23 11:08, Corinna Vinschen wrote: > On Mar 21 10:40, Takashi Yano wrote: > > Hi Corinna, > > > > On Fri, 20 Mar 2015 20:12:32 +0100 > > Corinna Vinschen wrote: > > > > > > For the time being, can you send your assignment as PDF via email > > > > to my company email address j

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Takashi, On Mar 21 10:40, Takashi Yano wrote: > Hi Corinna, > > On Fri, 20 Mar 2015 20:12:32 +0100 > Corinna Vinschen wrote: > > > > For the time being, can you send your assignment as PDF via email > > > to my company email address just so > > > we make sure it arrived in *some* way? > >

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Corinna, On Fri, 20 Mar 2015 20:12:32 +0100 Corinna Vinschen wrote: > > For the time being, can you send your assignment as PDF via email > > to my company email address just so > > we make sure it arrived in *some* way? > > Even better. We got legal approval that we can use signed PDFs vi

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Eric, On Mar 20 13:21, Eric Blake wrote: > On 03/20/2015 01:12 PM, Corinna Vinschen wrote: > > Even better. We got legal approval that we can use signed PDFs via > > email alone, and that sending snail mail isn't required anymore. > > Just sendthe PDF to . > > Awesome news! Shouldn't we updat

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

On 03/20/2015 01:12 PM, Corinna Vinschen wrote: > Even better. We got legal approval that we can use signed PDFs via > email alone, and that sending snail mail isn't required anymore. > Just sendthe PDF to . Awesome news! Shouldn't we update the contributor guideline html to match? -- Eric Blak

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Takashi, On Mar 19 09:34, Corinna Vinschen wrote: > On Mar 19 07:49, Takashi Yano wrote: > > Corinna Vinschen wrote: > > > Just to let you know I didn't forget about you, but your copyright > > > assignment still didn't make it to our office for some reason. > > > [...] > > On 5 March, I sent C

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Takashi, On Mar 19 07:49, Takashi Yano wrote: > Hi Corrina, s/rrin/rinn/ :) > On Wed, 18 Mar 2015 15:58:54 +0100 > Corinna Vinschen wrote: > > > Just to let you know I didn't forget about you, but your copyright > > assignment still didn't make it to our office for some reason. We > > check

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Corrina, On Wed, 18 Mar 2015 15:58:54 +0100 Corinna Vinschen wrote: > Just to let you know I didn't forget about you, but your copyright > assignment still didn't make it to our office for some reason. We > checked late yesterday again. I guess postal service is using rowboats > these days

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

On Mar 18 16:16, Bengt-Arne Fjellner wrote: > On 3/18/15 3:58 PM, Corinna Vinschen wrote: > >Hi Takashi, > > > >On Mar 2 21:05, Takashi Yano wrote: > >>On Sat, 28 Feb 2015 14:59:47 +0100 > >>Corinna Vinschen wrote: > >> > >>>As soon as we have your CA, we can discuss this patch further. > >> > >>

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

On 3/18/15 3:58 PM, Corinna Vinschen wrote: Hi Takashi, On Mar 2 21:05, Takashi Yano wrote: On Sat, 28 Feb 2015 14:59:47 +0100 Corinna Vinschen wrote: As soon as we have your CA, we can discuss this patch further. Can I send CA form by e-mail? Or should I send it as a postal mail? For t

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Takashi, On Mar 2 21:05, Takashi Yano wrote: > On Sat, 28 Feb 2015 14:59:47 +0100 > Corinna Vinschen wrote: > > > As soon as we have your CA, we can discuss this patch further. > > Can I send CA form by e-mail? Or should I send it as a postal mail? > > > For the time being, your patch is l

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

On Mar 5 19:22, Takashi Yano wrote: > On Mon, 2 Mar 2015 15:27:23 +0100 > Corinna Vinschen wrote: > > > > > As soon as we have your CA, we can discuss this patch further. > > > > > > Can I send CA form by e-mail? Or should I send it as a postal mail? > > > > Only postal so far, sorry. Maybe w

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

On Mon, 2 Mar 2015 15:27:23 +0100 Corinna Vinschen wrote: > > > As soon as we have your CA, we can discuss this patch further. > > > > Can I send CA form by e-mail? Or should I send it as a postal mail? > > Only postal so far, sorry. Maybe we can accept signed PDFs via email, > but I only just

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Takashi, On Mar 2 21:05, Takashi Yano wrote: > On Sat, 28 Feb 2015 14:59:47 +0100 > Corinna Vinschen wrote: > > > As soon as we have your CA, we can discuss this patch further. > > Can I send CA form by e-mail? Or should I send it as a postal mail? Only postal so far, sorry. Maybe we can

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

On Sat, 28 Feb 2015 14:59:47 +0100 Corinna Vinschen wrote: > As soon as we have your CA, we can discuss this patch further. Can I send CA form by e-mail? Or should I send it as a postal mail? > For the time being, your patch is lacking a ChangeLog entry. I scanned > your patch a bit, and it lo

Re: TIOCPKT mode of PTY is broken if ONLCR bit is cleared.

Hi Takashi, On Feb 28 14:36, Takashi Yano wrote: > Package: cygwin > Version: 1.7.34-6 It's terribly nice of you creating patches for Cygwin, and I'm really looking forward to include patches, but... there's a small problem. If you want to provide non-trivial patches (<= 10 lines) for the Cygwin

Re: sox - package is broken

On 20/03/2014 02:26, Christopher Faylor wrote: On Wed, Mar 19, 2014 at 08:46:51PM -0500, Yaakov (Cygwin/X) wrote: On 2014-03-19 19:39, Christopher Faylor wrote: On Wed, Mar 19, 2014 at 08:14:16PM +, David Stacey wrote: AUDIODRIVER=ao play ding.wav This is playing the audio through

Re: sox - package is broken

On Wed, Mar 19, 2014 at 08:46:51PM -0500, Yaakov (Cygwin/X) wrote: >On 2014-03-19 19:39, Christopher Faylor wrote: >> On Wed, Mar 19, 2014 at 08:14:16PM +, David Stacey wrote: >>> AUDIODRIVER=ao play ding.wav >>> >>> This is playing the audio through sox, which is where this whole thread >

Re: sox - package is broken

On 2014-03-19 19:39, Christopher Faylor wrote: On Wed, Mar 19, 2014 at 08:14:16PM +, David Stacey wrote: AUDIODRIVER=ao play ding.wav This is playing the audio through sox, which is where this whole thread started. No sound at all, and no output to the console to indicate that sox is a

Re: sox - package is broken

On Wed, Mar 19, 2014 at 08:14:16PM +, David Stacey wrote: >On 18/03/2014 23:16, Christopher Faylor wrote: >> On Tue, Mar 18, 2014 at 03:32:18PM -0400, Christopher Faylor wrote: >>> Ok. I see a SEGV with "cat >". Investigating. >> Should be fixed in the current snapshot. > >Thank you for takin

Re: sox - package is broken

On 2014-03-19 15:14, David Stacey wrote: AUDIODRIVER=ao play ding.wav This is playing the audio through sox, which is where this whole thread started. No sound at all, and no output to the console to indicate that sox is attempting to play the file. The command exits (with return code 0) af

Re: sox - package is broken

On 18/03/2014 23:16, Christopher Faylor wrote: On Tue, Mar 18, 2014 at 03:32:18PM -0400, Christopher Faylor wrote: Ok. I see a SEGV with "cat >". Investigating. Should be fixed in the current snapshot. Thank you for taking another look at this. I've tried with the latest snapshot, dated 20

Re: sox - package is broken

On Tue, Mar 18, 2014 at 05:49:48PM -0700, PolarStorm wrote: >David Stacey wrote >> I was testing with >> cat ding.wav > /dev/dsp >> This gives a segmentation fault with the latest (2014-03-18) snapshot; >> no sound is heard However, if I repeat your test: >> cp ding.wav /dev/dsp >> Then

Re: sox - package is broken

ould handle bit streamed input differently than a block copy/dump? -- View this message in context: http://cygwin.1069669.n5.nabble.com/Re-sox-package-is-broken-tp106970p107200.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems

Re: sox - package is broken

On Tue, Mar 18, 2014 at 03:32:18PM -0400, Christopher Faylor wrote: >Ok. I see a SEGV with "cat >". Investigating. > >FWIW, they are not the same. There's lots of dup'ing going on under >the hood with "cat >". Should be fixed in the current snapshot. cgf -- Problem reports: http://cygwi

Re: sox - package is broken

On Tue, Mar 18, 2014 at 07:29:14PM +, David Stacey wrote: >On 18/03/2014 17:53, Christopher Faylor wrote: >> On Mon, Mar 17, 2014 at 11:53:10PM +, David Stacey wrote: >>> On 17/03/2014 04:42, Christopher Faylor wrote: On Sun, Mar 16, 2014 at 10:28:29PM -0400, Christopher Faylor wrote:

Re: sox - package is broken

On 18/03/2014 17:53, Christopher Faylor wrote: On Mon, Mar 17, 2014 at 11:53:10PM +, David Stacey wrote: On 17/03/2014 04:42, Christopher Faylor wrote: On Sun, Mar 16, 2014 at 10:28:29PM -0400, Christopher Faylor wrote: On Sun, Mar 16, 2014 at 09:57:36PM -0400, Christopher Faylor wrote: O

Re: sox - package is broken

On Mon, Mar 17, 2014 at 11:53:10PM +, David Stacey wrote: >On 17/03/2014 04:42, Christopher Faylor wrote: >> On Sun, Mar 16, 2014 at 10:28:29PM -0400, Christopher Faylor wrote: >>> On Sun, Mar 16, 2014 at 09:57:36PM -0400, Christopher Faylor wrote: On Sun, Mar 16, 2014 at 10:36:31PM +,

Re: sox - package is broken

On 17/03/2014 04:42, Christopher Faylor wrote: On Sun, Mar 16, 2014 at 10:28:29PM -0400, Christopher Faylor wrote: On Sun, Mar 16, 2014 at 09:57:36PM -0400, Christopher Faylor wrote: On Sun, Mar 16, 2014 at 10:36:31PM +, David Stacey wrote: The issue I have is that close_audio_out() isn't

Re: sox - package is broken

On Mon, Mar 17, 2014 at 08:59:26AM +0100, Dr. Alexander Kleinsorge wrote: >thanks for all participants in this audio thread. >(I hope this post is auto-connected to the thread with this name - I >seldom use mailinglists. If not, sorry for that) > >This weekend, I was also woundering about the way t

Re: sox - package is broken

Hi thanks for all participants in this audio thread. (I hope this post is auto-connected to the thread with this name - I seldom use mailinglists. If not, sorry for that) This weekend, I was also woundering about the way the exit/stop/close is donw or if it can work. But I found another issue in

Re: sox - package is broken

On Mon, Mar 17, 2014 at 12:42:30AM -0400, Christopher Faylor wrote: >On Sun, Mar 16, 2014 at 10:28:29PM -0400, Christopher Faylor wrote: >>On Sun, Mar 16, 2014 at 09:57:36PM -0400, Christopher Faylor wrote: >>>On Sun, Mar 16, 2014 at 10:36:31PM +, David Stacey wrote: The issue I have is tha

Re: sox - package is broken

On Sun, Mar 16, 2014 at 10:28:29PM -0400, Christopher Faylor wrote: >On Sun, Mar 16, 2014 at 09:57:36PM -0400, Christopher Faylor wrote: >>On Sun, Mar 16, 2014 at 10:36:31PM +, David Stacey wrote: >>>The issue I have is that close_audio_out() isn't working as you'd >>>expect: for some reason,

Re: sox - package is broken

On Sun, Mar 16, 2014 at 09:57:36PM -0400, Christopher Faylor wrote: >On Sun, Mar 16, 2014 at 10:36:31PM +, David Stacey wrote: >>The issue I have is that close_audio_out() isn't working as you'd >>expect: for some reason, the 'audio_out_' member pointer is null > >This was because all of the I

Re: sox - package is broken

On Sun, Mar 16, 2014 at 10:36:31PM +, David Stacey wrote: >The issue I have is that close_audio_out() isn't working as you'd >expect: for some reason, the 'audio_out_' member pointer is null This was because all of the I/O operations were ignoring the archetype for the device. So, this is li

Re: sox - package is broken

On 16/03/2014 11:43, Corinna Vinschen wrote: If there are always samples at the end missing, maybe there's just some "flush audio queue" call missing in fhandler_dev_dsp::close_audio_out? I'm just glancing at this part of the code and what makes me a bit wary is the call audio_out_->stop (im

Re: sox - package is broken

On Mar 16 00:00, David Stacey wrote: > On 10/03/2014 11:14, Corinna Vinschen wrote: > >Does anybody feel up to the task to debug this issue in the Cygwin DLL? > >The DSP code is practically only in a single file called fhandler_dsp.cc. > > I've started looking at this, but it is at the very bottom

Re: sox - package is broken

On 10/03/2014 11:14, Corinna Vinschen wrote: Does anybody feel up to the task to debug this issue in the Cygwin DLL? The DSP code is practically only in a single file called fhandler_dsp.cc. I've started looking at this, but it is at the very bottom of my priority queue so progress might be sl

Re: sox - package is broken

> 1st sox problem: > in Cygwin 1.7.28 sound is broken. (sox + play) > I followed all hints as reply to my first post last week. > > $ play blip.wav > blip.wav: > File Size: 1.33k Bit Rate: 94.4k >Encoding: Unsigned PCM >Channel

Re: sox - package is broken

Hi Dave, yes, /dev/dsp seems to be broken. short wav-files are silent, long ones (> 2sec) are ok (hearable). Alexander -- On 26/02/2014 22:38, Dr. Alexander Kleinsorge wrote: 1st sox problem: in Cygwin 1.7.28 sound is broken. (sox + play) I followed all hints

Re: sox - package is broken

On 26/02/2014 22:38, Dr. Alexander Kleinsorge wrote: 1st sox problem: in Cygwin 1.7.28 sound is broken. (sox + play) I followed all hints as reply to my first post last week. $ play blip.wav blip.wav: File Size: 1.33k Bit Rate: 94.4k Encoding: Unsigned PCM Channels: 1 @ 8-bit

sox - package is broken

Hi Cygwin Team, 1st sox problem: in Cygwin 1.7.28 sound is broken. (sox + play) I followed all hints as reply to my first post last week. $ play blip.wav blip.wav: File Size: 1.33k Bit Rate: 94.4k Encoding: Unsigned PCM Channels: 1 @ 8-bit Samplerate: 11025Hz Replaygain: off Duration

RE: sox - package is broken

David Stacey sent the following at Monday, February 24, 2014 3:27 PM >On 24/02/2014 17:27, Dr. Alexander Kleinsorge wrote: >> But after (export AUDIODRIVER=ao ; play ding.wav) >> I see messages indicating successfull playing and application is waiting >> the time the wav-file takes, >> but no sound

Re: sox - package is broken

On 2014-02-24 11:27, Dr. Alexander Kleinsorge wrote: But after (export AUDIODRIVER=ao ; play ding.wav) I see messages indicating successfull playing and application is waiting the time the wav-file takes, but no sound. WFM. Does AUDIODRIVER=oss work? If you're still having problems, then pleas

Re: sox - package is broken

On 24/02/2014 17:27, Dr. Alexander Kleinsorge wrote: But after (export AUDIODRIVER=ao ; play ding.wav) I see messages indicating successfull playing and application is waiting the time the wav-file takes, but no sound. But I can hear the sound using VLC-win32 or WindowsMediaPlayer. You could tr

sox - package is broken

Hi Cygwin Team As reply for my Post: aplay (audio) support for cygwin - solution I got the hint to: " Install the Cygwin packages 'sox' and 'sox-fmt-*' " But installation of these sox packages is broken! I tried it on 3 computers and i have successfull installed C

gtk+2.0 is broken after upgrade.

Hello, I've upgraded my Cygwin (x86) installation the other day and now my all of my gtk+2.0 apps are crashing with segfaults. I've tested it against geda-gschem and geda-pcb as well as my own compiled programs. In general gtk seems to be working, but it always crashes whenever I try to op

Re: i686-w64-mingw32-gcc of cygwin64 is broken

On 9/26/2013 19:03, Frédéric Bron wrote: >> Compiled binary seems to crash here. >> I updated mingw64 runtime/headers yesterday. >> >> $ echo "main(){}" >t.c && i686-w64-mingw32-gcc t.c -o t >> $ ./t >> Segmentation fault > > These have been updated: > mingw64-*-headers-3.0.0-1 > mingw64-*-runtime

Re: i686-w64-mingw32-gcc of cygwin64 is broken

Hi, These have been updated: mingw64-*-headers-3.0.0-1 mingw64-*-runtime-3.0.0-1 w32api-{headers,runtime}-3.0.0-1 Thanks, but it seems I'm already using those version. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: i686-w64-mingw32-gcc of cygwin64 is broken

> Compiled binary seems to crash here. > I updated mingw64 runtime/headers yesterday. > > $ echo "main(){}" >t.c && i686-w64-mingw32-gcc t.c -o t > $ ./t > Segmentation fault These have been updated: mingw64-*-headers-3.0.0-1 mingw64-*-runtime-3.0.0-1 w32api-{headers,runtime}-3.0. 0-1 I wonder if

i686-w64-mingw32-gcc of cygwin64 is broken

Compiled binary seems to crash here. I updated mingw64 runtime/headers yesterday. $ echo "main(){}" >t.c && i686-w64-mingw32-gcc t.c -o t $ ./t Segmentation fault -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://

git-svn is broken

Currently, git-svn of Cygwin is unusable because of this: http://git.661346.n2.nabble.com/Git-pm-with-recent-File-Temp-fail-td7580381.html FYI, it was fixed on git 1.8.3: https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.3.txt -- Problem reports: http://cygwin.com/problems.h

RE: UDP/DTLS sockets communication pattern is broken in Cygwin

> > Too bad. I don't know the DTLS protocol, but isn't it possible to do the > server > part with a single UDP socket? If you keep track of the already connected > clients, you know if the just incoming packet is a connected or connecting > client, > and then you can use different threads to

Re: UDP/DTLS sockets communication pattern is broken in Cygwin

On Apr 12 08:44, Oleg Moskalenko wrote: > > > > > However, I think I found a workaround on the application level. > > Apparently all packets sent to a specific address are sent to the first > > socket > > which has been bound to the address. If that socket has been closed, the > > next in > >

  1   2   3   >