Re: fatal error: tcl.h: No such file or directory

2018-07-20 Thread S.J. Luo
ory > > > > How this could be?? > > > > *From:* Konovalov, Vadim [mailto:vadim.konova...@dell.com] > *Sent:* Friday, July 20, 2018 12:59 PM > *To:* S.J. Luo > *Cc:* tcltk@perl.org > > *Subject:* RE: fatal error: tcl.h: No such file or directory > >

Re: Tcl procedure 'winfo' not found at ...

2018-07-13 Thread S.J. Luo
Hi, I got subscribed here :) I have noticed the returned value '3 (wstat 768, 0x300)' from you differs from that of '2 (wstat 512, 0x200)' reported from CPAN tester. In my Cygwin environment, I also got a result 'Dubious, test returned 3 (wstat 768, 0x300)' if I run 'make test' without

Re: [rt.cpan.org #125472] error with coderefs passes as scalar args

2018-07-13 Thread S.J. Luo
2018-07-07 22:46 GMT+08:00 huck : > > Yes, as we saw when code disposal was introduced , even existing > applications can be ruined if care is not properly taken. Maybe if > create_tcl_sub() had been documented as part of the api this problem would > not have been created in the first place. >

Re: fatal error: tcl.h: No such file or directory

2018-07-19 Thread S.J. Luo
> but we do have these lines I Makefile.PL now: > > ... > $incpath = $tclcfg{TCL_INCLUDE_SPEC}; > > # https://www.cpantesters.org/cpan/report/18397198-6bf4-1014-85e5-4e79f459b9c5 > # Tcl.xs:32:10: fatal error: tcl.h: No such file or directory > if ($incpath) { > my @tclh = grep {-f "$_/tcl.h"}

Re: Possible bug in Tcl.pm exposed by Tktable?

2020-03-25 Thread S.J. Luo
ot;set env"), we will get segmentation fault on it immediately, before exiting of Perl. So far I am not able to come out a simple way to get it fixed. I think either Tcl should not change the environment globally, or there should be some way to inform Perl that environment variables has b

Re: Possible bug in Tcl.pm exposed by Tktable?

2020-03-22 Thread S.J. Luo
Hi, I'd like to share my finding. I also duplicated the error on CentOS 7, who comes with perl 5.16 installed and tcl-8.5. while on my Cygwin build there is no problem. After some tracing, I found the error point is at the perl_destruct() calling Perl_safesysfree() in perl.c: