Re: [pcre-dev] Preparation for using JIT under S390

2020-11-21 Thread Ze'ev Atlas via Pcre-dev
For some reason I do not receive all emails from pcre-dev, so I am answering my own email.   I tried several attempts to disengage the code from the 'Linux only' approach.  Unfortunately, this is unnecessarily too involved and include usage of non-standard (outside of *nix world) headers such

Re: [pcre-dev] PCRE2 10.35 testing issues on Windows

2020-11-21 Thread Ze'ev Atlas via Pcre-dev
Hi PhilI see that this involved an open file command which means that you have to supply the filename, potentially fully qualified filename.  That brings a few questions: 1. Why should the onus of fixing this be on you rather than on the user, who should supply a fully qualified file name? 2.

Re: [pcre-dev] PCRE2 10.35 testing issues on Windows

2020-11-21 Thread Philip Hazel via Pcre-dev
I have fixed the RunTest script by making it copy testdata/testbtables to the current directory before running test 2 (which now looks for ./testdata). Please can you advise me on the correct command to add to RunTest.bat to make it do the same. Is this right? copy %srcdir%\testdata\testbtables

Re: [pcre-dev] PCRE2 10.35 testing issues on Windows

2020-11-21 Thread Philip Hazel via Pcre-dev
Thank you for reporting this. It turns out not to be Windows-specific, so I can't use the "I'm not a Windows user" excuse. The same problem occurs when building in a directory well out of the source directory on Linux. However, a bug in the RunTest script prevented this failure from being