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 Some tests may complain under known circumstances. See
18 below and hints/qnx.sh for more information.
20 Under QNX 6.1.0 there are still a few tests which fail.
21 See below and hints/qnx.sh for more information.
23 =head2 Required Software for Compiling Perl on QNX4
25 As with many unix ports, this one depends on a few "standard"
26 unix utilities which are not necessarily standard for QNX4.
32 This is used heavily by Configure and then by
33 perl itself. QNX4's version is fine, but Configure
34 will choke on the 16-bit version, so if you are
35 running QNX 4.22, link /bin/sh to /bin32/ksh
39 This is the standard unix library builder.
40 We use wlib. With Watcom 10.6, when wlib is
41 linked as "ar", it behaves like ar and all is
42 fine. Under 9.5, a cover is required. One is
47 This is used (optionally) by configure to list
48 the contents of libraries. I will generate
49 a cover function on the fly in the UU directory.
53 Configure and perl need a way to invoke a C
54 preprocessor. I have created a simple cover
55 for cc which does the right thing. Without this,
56 Configure will create its own wrapper which works,
57 but it doesn't handle some of the command line arguments
58 that perl will throw at it.
62 You really need GNU make to compile this. GNU make
63 ships by default with QNX 4.23, but you can get it
64 from quics for earlier versions.
68 =head2 Outstanding Issues with Perl on QNX4
70 There is no support for dynamically linked libraries in QNX4.
72 If you wish to compile with the Socket extension, you need
73 to have the TCP/IP toolkit, and you need to make sure that
74 -lsocket locates the correct copy of socket3r.lib. Beware
75 that the Watcom compiler ships with a stub version of
76 socket3r.lib which has very little functionality. Also
77 beware the order in which wlink searches directories for
78 libraries. You may have /usr/lib/socket3r.lib pointing to
79 the correct library, but wlink may pick up
80 /usr/watcom/10.6/usr/lib/socket3r.lib instead. Make sure
81 they both point to the correct library, that is,
82 /usr/tcptk/current/usr/lib/socket3r.lib.
84 The following tests may report errors under QNX4:
86 ext/Cwd/Cwd.t will complain if `pwd` and cwd don't give
87 the same results. cwd calls `fullpath -t`, so if you
88 cd `fullpath -t` before running the test, it will
91 lib/File/Find/taint.t will complain if '.' is in your
92 PATH. The PATH test is triggered because cwd calls
95 ext/IO/lib/IO/t/io_sock.t: Subtest 14 is skipped due to
96 the fact that the functionality to read back the non-blocking
97 status of a socket is not implemented in QNX's TCP/IP. This
98 has been reported to QNX and it may work with later versions
101 =head2 QNX auxiliary files
103 The files in the "qnx" directory are:
109 A script that emulates the standard unix archive (aka library)
110 utility. Under Watcom 10.6, ar is linked to wlib and provides the
111 expected interface. With Watcom 9.5, a cover function is
112 required. This one is fairly crude but has proved adequate for
117 A script that provides C preprocessing functionality. Configure can
118 generate a similar cover, but it doesn't handle all the command-line
119 options that perl throws at it. This might be reasonably placed in
124 =head2 Outstanding issues with perl under QNX6
126 The following tests are still failing for Perl 5.7.3 under QNX 6.1.0:
128 op/sprintf.........................FAILED at test 91
129 lib/Benchmark......................FAILED at test 26
131 This is due to a bug in the C library's printf routine.
132 printf("'%e'", 0. ) produces '0.000000e+0', but ANSI requires
133 '0.000000e+00'. QNX has acknowledged the bug and it should be
138 Norton T. Allen (allen@huarp.harvard.edu)