It appears that on $^O MSWin32 both perl-5.8.4, 5.6.1 are good with our
"Makefile.PL",
Also "Cygwin" is good, and obviously "linux" + freebsd
Perl-5.12 5.16 5.16 and 5.28 all fail with
error starting tclsh: $?=-1; $!=Inappropriate I/O control operation
error writing "stdout": broken pipe
while executing
"puts "tclsh=[info nameofexecutable]""
(file "tclcfg.tcl" line 1)
IMO this is MSWin32 incompatibility WRT "$?" var.
What we need to do is workaround which will ignore $? on win32.
Report with perlbug to [email protected]?
-----Original Message-----
From: Konovalov, Vadim [mailto:[email protected]]
Sent: Monday, August 20, 2018 11:39 PM
To: Christopher Chavez; [email protected]
Subject: RE: Error running Makefile.PL on Windows
OMG you're correct
Will have a closer look tomorrow
-----Original Message-----
From: Christopher Chavez [mailto:[email protected]]
Sent: Monday, August 20, 2018 11:01 PM
To: [email protected]
Subject: Re: Error running Makefile.PL on Windows
On 8/20/2018 2:36 PM, Konovalov, Vadim wrote:
>> I have a machine with Windows 10 64-bit 1803, ActivePerl* 5.24.3, and
>> ActiveTcl 8.6.7.
>>
>> *(Uses dmake and doesn't have gnu make. I'm not constrained to
>> ActivePerl; I just didn't know about Strawberry until recently.)
>
> If you think that "dmake" is source of trouble, then we can add
> workaround in Makefile.PL to handle your case.
>
> You can add a code that checks these vars $? and $! differently
>
> fortunately, our Makefile.PL already has a stub to deal with dmake, so
> you can benefit from it.
>
Fortunately I haven't encountered an issue with dmake specifically. I was
checking to see if the past few commits of Tcl.pm would compile, and found the
one from a few weeks ago when there were some suspicions over dmake causing
compilation issues. The "dmake prohibited" message seemed to confuse ActivePerl
for "modified" Strawberry Perl installation due to presence of dmake/lack of
GNU make. But that message has since been reverted since the problem (if there
is one) is believed to be elsewhere.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
