Re: perl -- classic?

2019-02-04 Thread Wayne Davison
On Mon, Feb 4, 2019 at 2:33 PM L A Walsh wrote: > Things like > Term::Size::chars no longer works as it says chars isn't exported. > but it is 'EXPORT_OK', and it used to work. Remember that EXPORT_OK means that you can ask for it to be exported, but it's not by default. I just tried out CPAN

Re: perl -- classic?

2019-02-04 Thread Peter A. Castro
On Mon, Feb 04, 2019 at 02:32:35PM -0800, L A Walsh wrote: Greetings, > Can we have an older perl, say, perl-5.0.16? works for my stuff mostly > unchanged, You sure you mean 5.0.16? That's really, really old! Maybe you mean 5.16.1? The earliest perl version I have in my archives for Cygwin

perl -- classic?

2019-02-04 Thread L A Walsh
Can we have an older perl, say, perl-5.0.16? works for my stuff mostly unchanged, I can't get many cpan things to work with current perl. Things like Term::Size::chars no longer works as it says chars isn't exported. but it is 'EXPORT_OK', and it used to work. Too many things break on cpan on

Restaurant Canada Show 2019

2019-02-04 Thread Ruby Jaxson via cygwin
Hi, I am following up to check if your company is interested in acquiring Attendees List World of Asphalt 2019? Expo Details: Date: FEBRUARY 12-14, 2019 Location: INDIANAPOLIS, IN, USA. Expo Name: World of Asphalt 2019 Total Attendees Count: 6,000+Attendees Data Fields

[newlib-cygwin] Cygwin: timerfd: drop outdated TODO comment

2019-02-04 Thread Corinna Vinschen
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=99cd3df6ec471d6cbdea62fb14ebbe1e5eec8ef8 commit 99cd3df6ec471d6cbdea62fb14ebbe1e5eec8ef8 Author: Corinna Vinschen Date: Mon Feb 4 21:08:03 2019 +0100 Cygwin: timerfd: drop outdated TODO comment Signed-off-by: Corinna

Re: 32 bit vs 64 bit Cygwin, followup

2019-02-04 Thread Corinna Vinschen
On Feb 4 09:16, Sam Habiel wrote: > >That's not GCC fault. You're running varargs, written for the standard > >stack layout of the MSABI target from a function with a stack laid out > >in SYSV ABI. That can't work. > > I did some research to see how to write my own version of varargs (the >

Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.3

2019-02-04 Thread Corinna Vinschen
On Feb 4 14:19, Michael Haubenwallner wrote: > On 2/3/19 12:19 PM, Corinna Vinschen wrote: > > On Jan 31 20:48, Corinna Vinschen wrote: > >> On Jan 31 09:47, Michael Haubenwallner wrote: > >>> Hi Corinna, > >>> > >>> I'm missing that topic/forkables branch in the announcement - is that in? > >>>

Re: 32 bit vs 64 bit Cygwin, followup

2019-02-04 Thread Sam Habiel
>That's not GCC fault. You're running varargs, written for the standard >stack layout of the MSABI target from a function with a stack laid out >in SYSV ABI. That can't work. I did some research to see how to write my own version of varargs (the code base is already instrumented to do different

Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.3

2019-02-04 Thread Michael Haubenwallner
On 2/3/19 12:19 PM, Corinna Vinschen wrote: > On Jan 31 20:48, Corinna Vinschen wrote: >> On Jan 31 09:47, Michael Haubenwallner wrote: >>> Hi Corinna, >>> >>> I'm missing that topic/forkables branch in the announcement - is that in? >>> https://cygwin.com/ml/cygwin-patches/2017-q1/msg00053.html