From: John E. Malmberg [mailto:[EMAIL PROTECTED]
> Paul Marquess wrote:
> > From: John E. Malmberg
> <much snipping >
> >>>
> >>> From what I have seen of the other tests, the INC setting when running
> >>>these tests is usually inherited from the parent, and I have seen the
> >>>tests use a test when deciding to use blib or not.
> >>>
> >>>I did not know the correct fix, just what I needed to stop the script
> >>>from failing so soon. The [-.lib] was the only place that I could find
> >>>the modules. That is also the setting that was passed on the command
> >>>line to 03examples.t.
> >>
> >>Is there really any reason that there is VMS specific code here?
> >
> >
> > What happens if you remove it?
>
> It works the same way as with the last patch. Apparently VMS does not
> need to be special cased here.
OK, I'll remove that code from my development copy.
This leaves the case where C::Zlib is built away from the core, which is
what the original code did
$Inc = '-"I[.blib.lib]" -"I[.blib.arch]"'
Once someone gets around to building C::Zlib away from the core we can
revisit this.
> Tests 8,9,10,12,13 still fail for an unknown reason that I have not had
> time to investigate.
Tests 10-13 all pass the STDIN filehandle to zlib. We discussed this earlier
in the thread.
The only thing different about Tests 8 and 9 is that the test uses two
invocations of Perl with a "unix pipe" between them
$Perl $Inc ${examples}/filtdef $file1 $file2 | $Perl $Inc
${examples}/filtinf 2>$stderr
Are there any issue with this on VMS? Perhaps there is an issue with passing
binary data through the pipe?
Paul
