Re: [ITP] alure 1.2

2016-10-17 Thread Bastian Germann
This is actually a bug (different variable names in FindFLAC.cmake and CMakeLists.txt) that was fixed implicitly upstream with http://repo.or.cz/alure.git/commit/6934c17f9ace7fc19ea94623dab0a4b37d11a879 I added a patch for v1.2 and also included support for fluidsynth. Now all dependencies that

Re: setup-x86.exe BAD signature from "Cygwin <cygwin@cygwin.com>"

2016-10-17 Thread Lee
On 10/17/16, Thomas Sanders wrote: > Am I doing something wrong here? > > gpg --verify setup-x86.exe.sig setup-x86.exe > > gpg: Signature made Fri 09 Sep 2016 02:20:02 AM PDT using DSA key ID > 676041BA > gpg: BAD signature from "Cygwin " > > If I am not doing something wrong,

RE: Errors using configure when building packages

2016-10-17 Thread Sinkler, Wharton
Yes that did it. The problem was definitely caused by virus scan - McAfee. Not sure why, but excluding the folder from on-access scanner did not get rid of the error. Only by completely disabling Access Protection and On-Access Scanner in the McAfee console was I able to complete the

Re: [ITP] alure 1.2

2016-10-17 Thread Bastian Germann
2016-10-17 21:38 GMT+02:00 Ken Brown : > That happens because DYNLOAD is not defined. If you build with DYNLOAD > defined, it links fine. There is one glitch that has to be fixed when you > do that. The build detects windows.h and then doesn't include dlfcn.h. > [See main.h,

setup-x86.exe BAD signature from "Cygwin <cygwin@cygwin.com>"

2016-10-17 Thread Thomas Sanders
Am I doing something wrong here? gpg --verify setup-x86.exe.sig setup-x86.exe gpg: Signature made Fri 09 Sep 2016 02:20:02 AM PDT using DSA key ID 676041BA gpg: BAD signature from "Cygwin " If I am not doing something wrong, this has been going on for a few weeks. Please

Re: Errors using configure when building packages

2016-10-17 Thread cyg Simple
On 10/14/2016 4:23 PM, Ken Brown wrote: > On 10/14/2016 1:46 PM, Sinkler, Wharton wrote: >> I've got a new Cygwin installation on Win7, which has issues with >> configure, the first step of building packages from source (I've seen >> this with ImageMagick, libtiff and others so it's not specific

Re: [ITP] alure 1.2

2016-10-17 Thread Ken Brown
On 10/17/2016 9:41 AM, Bastian Germann wrote: Am 16.10.2016 um 23:30 schrieb Marco Atzeri: Any reason to not add FLAC (Free Lossless Audio Codec) dependency ? Yes, there is a reason: The symbols used from FLAC/stream_decoder.h cannot be linked: [ 70%] Linking CXX shared library

Re: Errors using configure when building packages

2016-10-17 Thread Linda Walsh
Sinkler, Wharton wrote: I've got a new Cygwin installation on Win7, which has issues with configure, the first step of building packages from source (I've seen this with ImageMagick, libtiff and others so it's not specific to the package I'm installing). It seems to sporadically be unable to

Re: /dev/stderr problem

2016-10-17 Thread Linda Walsh
Eric Blake wrote: On 10/17/2016 01:32 AM, Thorsten Kampe wrote: * Thorsten Kampe (Mon, 17 Oct 2016 08:25:13 +0200) the following bash script results in a different output when redirected to a file. ``` printf "FIRST LINE\n" > /dev/stderr shopt -os xtrace printf "SECOMD LINE\n" > /dev/stderr

Re: /dev/stderr problem

2016-10-17 Thread Eric Blake
On 10/17/2016 01:32 AM, Thorsten Kampe wrote: > * Thorsten Kampe (Mon, 17 Oct 2016 08:25:13 +0200) > >> the following bash script results in a different output when >> redirected to a file. >> >> ``` >> printf "FIRST LINE\n" > /dev/stderr >> shopt -os xtrace >> printf "SECOMD LINE\n" >

Re: [ITP] alure 1.2

2016-10-17 Thread Bastian Germann
Am 16.10.2016 um 23:30 schrieb Marco Atzeri: > However I suggest to not build the static library > and to install only the shared one, as this is the default > on cygwin. Ok. > Any reason to not add FLAC (Free Lossless Audio Codec) > dependency ? Yes, there is a reason: The symbols used from

Re: /dev/stderr problem

2016-10-17 Thread Thorsten Kampe
* Thorsten Kampe (Mon, 17 Oct 2016 08:25:13 +0200) > the following bash script results in a different output when > redirected to a file. > > ``` > printf "FIRST LINE\n" > /dev/stderr > shopt -os xtrace > printf "SECOMD LINE\n" > /dev/stderr > ``` On further inspection: the `xtrace` is not

/dev/stderr problem

2016-10-17 Thread Thorsten Kampe
Hi, the following bash script results in a different output when redirected to a file. ``` printf "FIRST LINE\n" > /dev/stderr shopt -os xtrace printf "SECOMD LINE\n" > /dev/stderr ``` ``` $ bash script.sh FIRST LINE + printf 'SECOMD LINE\n' SECOMD LINE ``` ``` $ bash script.sh 2> file && cat