Re: Upstream Spectre CVE Patch Availability

2018-01-18 Thread Yaakov Selkowitz
On 2018-01-18 19:45, Brian Inglis wrote: > Not seen any posts here about the monster in the chip yet (although those who > might know may be busy dealing with the issues in their jobs), so has anyone > any > idea if or when we might see upstream Spectre CVE patches available for the > following pa

Re: Upstream Spectre CVE Patch Availability

2018-01-18 Thread Brian Inglis
On 2018-01-18 18:45, Brian Inglis wrote: > Hi folks, > > Not seen any posts here about the monster in the chip yet (although those who > might know may be busy dealing with the issues in their jobs), so has anyone > any > idea if or when we might see upstream Spectre CVE patches available for the

Upstream Spectre CVE Patch Availability

2018-01-18 Thread Brian Inglis
Hi folks, Not seen any posts here about the monster in the chip yet (although those who might know may be busy dealing with the issues in their jobs), so has anyone any idea if or when we might see upstream Spectre CVE patches available for the following packages, whose bases have been mentioned i

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.10.0-0.1

2018-01-18 Thread Ken Brown
On 1/18/2018 4:30 PM, Yaakov Selkowitz wrote: On 2018-01-18 08:35, Ken Brown wrote: On 1/17/2018 5:29 PM, Ken Brown wrote: Do we need a new gcc release to go along with the recent ssp changes? The following commit message seems to answer my question:     Note that this does require building

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.10.0-0.1

2018-01-18 Thread Yaakov Selkowitz
On 2018-01-18 08:35, Ken Brown wrote: > On 1/17/2018 5:29 PM, Ken Brown wrote: >> Do we need a new gcc release to go along with the recent ssp changes? > > The following commit message seems to answer my question: > >     Note that this does require building gcc with --disable-libssp and >     gc

Re: Monit Compilation Errors

2018-01-18 Thread szgyg
On 2018-01-18, BGINFO4X wrote: > 2018-01-17 20:12 GMT+01:00 szgyg : Please don't quote raw email addresses. > Finally, fter switching to the 32bits cygwin version (-m32 in cygwin64 > generated more errors), and modifying Lync.c , monit has b

Re: deleted current directory behaviour

2018-01-18 Thread Achim Gratz
Tony Cook writes: > Currently cygwin emulates* Linux (and most other POSIXish systems that > I'm aware of) by allowing the current directory to be removed: […] > Is that inconsistency with other platforms intentional? It's one of those non-POSIXy things that can be detected if you look closely eno

Re: Monit Compilation Errors

2018-01-18 Thread BGINFO4X
Hello again, Yes, you are right, --ansi have undesirable effects like: In file included from src/net.h:30:0, from src/p.y:120: src/monit.h:124:1: error: C++ style comments are not allowed in ISO C90 //FIXME: we can export this type in libmonit ^ etc ... Finally, fter switching

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.10.0-0.1

2018-01-18 Thread Ken Brown
On 1/17/2018 5:29 PM, Ken Brown wrote: On 1/16/2018 10:51 AM, Corinna Vinschen wrote: Hi folks, I uploaded a new Cygwin test release 2.10.0-0.1 I'm planning for a release end of January.  Please test. Do we need a new gcc release to go along with the recent ssp changes? The following comm