1 If you read this file _as_is_, just ignore the funny characters you see.
2 It is written in the POD format (see pod/perlpod.pod) which is specially
3 designed to be readable as is.
7 README.qnx - Perl version 5 on QNX
11 As of perl5.7.2 all tests pass under:
14 Watcom 10.6 with Beta/970211.wcc.update.tar.F
15 socket3r.lib Nov21 1996.
17 As of perl5.8.1 there is at least one test still failing.
19 Some tests may complain under known circumstances.
21 See below and hints/qnx.sh for more information.
23 Under QNX 6.2.0 there are still a few tests which fail.
24 See below and hints/qnx.sh for more information.
26 =head2 Required Software for Compiling Perl on QNX4
28 As with many unix ports, this one depends on a few "standard"
29 unix utilities which are not necessarily standard for QNX4.
35 This is used heavily by Configure and then by
36 perl itself. QNX4's version is fine, but Configure
37 will choke on the 16-bit version, so if you are
38 running QNX 4.22, link /bin/sh to /bin32/ksh
42 This is the standard unix library builder.
43 We use wlib. With Watcom 10.6, when wlib is
44 linked as "ar", it behaves like ar and all is
45 fine. Under 9.5, a cover is required. One is
50 This is used (optionally) by configure to list
51 the contents of libraries. I will generate
52 a cover function on the fly in the UU directory.
56 Configure and perl need a way to invoke a C
57 preprocessor. I have created a simple cover
58 for cc which does the right thing. Without this,
59 Configure will create its own wrapper which works,
60 but it doesn't handle some of the command line arguments
61 that perl will throw at it.
65 You really need GNU make to compile this. GNU make
66 ships by default with QNX 4.23, but you can get it
67 from quics for earlier versions.
71 =head2 Outstanding Issues with Perl on QNX4
73 There is no support for dynamically linked libraries in QNX4.
75 If you wish to compile with the Socket extension, you need
76 to have the TCP/IP toolkit, and you need to make sure that
77 -lsocket locates the correct copy of socket3r.lib. Beware
78 that the Watcom compiler ships with a stub version of
79 socket3r.lib which has very little functionality. Also
80 beware the order in which wlink searches directories for
81 libraries. You may have /usr/lib/socket3r.lib pointing to
82 the correct library, but wlink may pick up
83 /usr/watcom/10.6/usr/lib/socket3r.lib instead. Make sure
84 they both point to the correct library, that is,
85 /usr/tcptk/current/usr/lib/socket3r.lib.
87 The following tests may report errors under QNX4:
89 ext/Cwd/Cwd.t will complain if `pwd` and cwd don't give
90 the same results. cwd calls `fullpath -t`, so if you
91 cd `fullpath -t` before running the test, it will
94 lib/File/Find/taint.t will complain if '.' is in your
95 PATH. The PATH test is triggered because cwd calls
98 ext/IO/lib/IO/t/io_sock.t: Subtests 14 and 22 are skipped due to
99 the fact that the functionality to read back the non-blocking
100 status of a socket is not implemented in QNX's TCP/IP. This has
101 been reported to QNX and it may work with later versions of
104 t/io/tell.t: Subtest 27 is failing. We are still investigating.
106 =head2 QNX auxiliary files
108 The files in the "qnx" directory are:
114 A script that emulates the standard unix archive (aka library)
115 utility. Under Watcom 10.6, ar is linked to wlib and provides the
116 expected interface. With Watcom 9.5, a cover function is
117 required. This one is fairly crude but has proved adequate for
122 A script that provides C preprocessing functionality. Configure can
123 generate a similar cover, but it doesn't handle all the command-line
124 options that perl throws at it. This might be reasonably placed in
129 =head2 Outstanding issues with perl under QNX6
131 The following tests are still failing for Perl 5.8.1 under QNX 6.2.0:
133 op/sprintf.........................FAILED at test 91
134 lib/Benchmark......................FAILED at test 26
136 This is due to a bug in the C library's printf routine.
137 printf("'%e'", 0. ) produces '0.000000e+0', but ANSI requires
138 '0.000000e+00'. QNX has acknowledged the bug.
142 Norton T. Allen (allen@huarp.harvard.edu)