Re: setup-x86.exe BAD signature from "Cygwin "

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, this has been going on for a few weeks.
> Please advise either way.

works for me
$ gpg --verify cygwinSetup-x86.exe.sig cygwinSetup-x86.exe
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/documentation/faqs.html for more
information
gpg: Signature made Fri Sep  9 05:20:02 2016 EDT using DSA key ID 676041BA
gpg: Good signature from "Cygwin "
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1169 DF9F 2273 4F74 3AA5  9232 A9A2 62FF 6760 41BA

have you tried downloading from both home & work?  to different machines?

Lee

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



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 configure script for 
ImageMagick on my Cygwin installation.  

Thanks for the help and hope this will help others who encounter this problem.  

-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of Ken 
Brown
Sent: Friday, October 14, 2016 3:23 PM
To: cygwin@cygwin.com
Subject: Re: Errors using configure when building packages

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 to the package I'm 
> installing).
>
> It seems to sporadically be unable to remove a file 'conftest.exe' which is 
> compiled in the tests within configure.  This shows up during configure as:
>
> rm: cannot remove 'conftest.exe': Device or resource busy
>
> The configure will then fail completely when this causes a critical test to 
> fail.
>
> I suspect that this might have something to do with slowness to release an 
> in-use file (the conftest.exe) in the Win7 operating system.  I've searched 
> the archives and don't see this exact issue showing up in previous posts.  
> Have others experienced this problem?  Is there a fix which will allow me to 
> complete building these packages?

Do you have security software installed that might be interfering with Cygwin?

Ken


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



setup-x86.exe BAD signature from "Cygwin "

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 advise either way.
Thanks!

 -- 
Thomas Sanders | Sr. Network Systems Administrator
TrellisWare Technologies, Inc.

Office/FAX: 858-753-1654 | Mobile: 619-512-3311


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



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 to the
>> package I'm installing).
>>
>> It seems to sporadically be unable to remove a file 'conftest.exe'
>> which is compiled in the tests within configure.  This shows up during
>> configure as:
>>
>> rm: cannot remove 'conftest.exe': Device or resource busy
>>
>> The configure will then fail completely when this causes a critical
>> test to fail.
>>
>> I suspect that this might have something to do with slowness to
>> release an in-use file (the conftest.exe) in the Win7 operating
>> system.  I've searched the archives and don't see this exact issue
>> showing up in previous posts.  Have others experienced this problem? 
>> Is there a fix which will allow me to complete building these packages?
> 
> Do you have security software installed that might be interfering with
> Cygwin?
> 

This is often an issue of your security software having opened the
conftest.exe for inspection and the configure script expects to delete
it but cannot because it is now opened by another process.  Exclude your
working directory from the scan to resolve it.

-- 
cyg Simple

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



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 remove a file 'conftest.exe' which is 
compiled in the tests within configure.  This shows up during configure as:

rm: cannot remove 'conftest.exe': Device or resource busy

The configure will then fail completely when this causes a critical test to fail.  

I suspect that this might have something to do with slowness to release an in-use file (the conftest.exe) in the Win7 operating system.  I've searched the archives and don't see this exact issue showing up in previous posts.  Have others experienced this problem?  Is there a fix which will allow me to complete building these packages? 


I ran into a similar problem on linux - but was unable to
describe it to the point where others could reproduce it -- so I 
manually worked around it in each case where it happened, until some
SW-update to the autoconf-stuff made it go away.  It also happened in 
multiple packages, so wasn't specific to any one -- but it also 
happened on *linux*.


The problem is that somehow the information for "conftest.exe" will
be *in* the directory "conftest.exe" with some temporary name.  It's 
really a weird one -- but it happened with different files (where

the actual file was in a directory that had the name of the file, and
the actual file being in the directory with some name like "out".

It happened with multiple SW products that I would build, but not
most.  Have no idea what caused it but do know that updating the
autoconf-related SW eventually made it go away.  Sorry can't be
more precise, but when I tried reporting it as a bug, different
dev-teams gave up and suggested re-formatting and re-installing 
linux.  So helpful!  


Occasionally I run into weird problems -- because of how my system
is setup -- but are still caused by bugs in the underlying SW --
like making perl, completely failed for a few years on my system
because I had a RAID 50 where the "optimal write size" was 12*64KB
(3 RAID-5's that were 4*64KB/stripe).  The underlying Gnu DB library
failed (probably still does, as no one wanted to try to fix it, 
was designed around the assumption that the optimal-write-size
would always be a power-of-2 -- which it is not.  


I even told how to reproduce and test for it (using a VM), but
it got ignored... ;^/



--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



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


Cygwin treats '> /dev/stderr' as a request to truncate /dev/stderr (or,
for that matter, any opening of a file under /proc/self/fd).  Other
platforms treat that as a special file that can never be truncated, but
is instead reopened at the same offset.

Maybe cygwin can be taught that opening a file through /proc/self/fd
should preserve rather than reset offsets, but it will be a tricky
patch, and someone has to write it.

---
Is /dev/stderr a POSIX special name that one should expect that rewinding
is disallowed or ignored?

Good analysis, BTW, that sure would have puzzled me.
-l






--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



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" > /dev/stderr

Cygwin treats '> /dev/stderr' as a request to truncate /dev/stderr (or,
for that matter, any opening of a file under /proc/self/fd).  Other
platforms treat that as a special file that can never be truncated, but
is instead reopened at the same offset.

Maybe cygwin can be taught that opening a file through /proc/self/fd
should preserve rather than reset offsets, but it will be a tricky
patch, and someone has to write it.

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature