save a dTHX

[p5sagit/p5-mst-13.2.git] / README.qnx

diff --git a/README.qnx b/README.qnx
index ebff548..f59455b 100644 (file)
--- a/README.qnx
+++ b/README.qnx
@@ -8,13 +8,22 @@ README.qnx - Perl version 5 on QNX
 
 =head1 DESCRIPTION
 
-As of perl5.004_04, all tests pass under:
+As of perl5.8.0 all tests pass under:
 
-  QNX 4.23A
+  QNX 4.24G
   Watcom 10.6 with Beta/970211.wcc.update.tar.F
   socket3r.lib Nov21 1996.
 
-Update June 2001: Perl 5.6.1 most probably also works just fine in QNX.
+Some tests may complain under known circumstances. See
+below and hints/qnx.sh for more information.
+
+[ Perl 5.6.0 is shipping with QNX RTP (aka QNX6, Neutrino), but
+the build does not appear to be straightforward. If anyone has
+more data in this regard, please let me know.
+
+These notes were originally written for QNX4 and do not
+necessarily apply to Neutrino, but see hints/qnx.sh for
+more information. ] 
 
 =head2 Required Software for Compiling Perl on QNX
 
@@ -49,7 +58,7 @@ a cover function on the fly in the UU directory.
 Configure and perl need a way to invoke a C
 preprocessor. I have created a simple cover
 for cc which does the right thing. Without this,
-Configure will create it's own wrapper which works,
+Configure will create its own wrapper which works,
 but it doesn't handle some of the command line arguments
 that perl will throw at it.
 
@@ -63,7 +72,24 @@ from quics for earlier versions.
 
 =head2 Outstanding Issues with Perl on QNX
 
-There is currently no support for dynamically linked libraries.
+There is no support for dynamically linked libraries in QNX4.
+
+The following tests may report errors:
+
+ext/Cwd/Cwd.t will complain if `pwd` and cwd don't give
+the same results. cwd calls `fullpath -t`, so if you
+cd `fullpath -t` before running the test, it will
+pass.
+
+lib/File/Find/taint.t will complain if '.' is in your
+PATH. The PATH test is triggered because cwd calls
+`fullpath -t`.
+
+ext/IO/lib/IO/t/io_sock.t: Subtest 14 is skipped due to
+the fact that the functionality to read back the non-blocking
+status of a socket is not implemented in QNX's TCP/IP. This
+has been reported to QNX and it may work with later versions
+of TCP/IP.
 
 =head2 QNX auxiliary files