Daftar Isi

• NAME
• DESCRIPTION
  • Required Software for Compiling Perl on QNX4
  • Outstanding Issues with Perl on QNX4
  • QNX auxiliary files
  • Outstanding issues with perl under QNX6
• AUTHOR

NAME

perlqnx - Perl version 5 on QNX

DESCRIPTION

As of perl5.7.2 all tests pass under:

  QNX 4.24G
 
  Watcom 10.6 with Beta/970211.wcc.update.tar.F
 
  socket3r.lib Nov21 1996.
 

As of perl5.8.1 there is at least one test still failing.

Some tests may complain under known circumstances.

See below and hints/qnx.sh for more information.

Under QNX 6.2.0 there are still a few tests which fail.See below and hints/qnx.sh for more information.

Required Software for Compiling Perl on QNX4

As with many unix ports, this one depends on a few "standard"unix utilities which are not necessarily standard for QNX4.

• /bin/sh

  This is used heavily by Configure and then byperl itself. QNX4's version is fine, but Configurewill choke on the 16-bit version, so if you arerunning QNX 4.22, link /bin/sh to /bin32/ksh

• ar

  This is the standard unix library builder.We use wlib. With Watcom 10.6, when wlib islinked as "ar", it behaves like ar and all isfine. Under 9.5, a cover is required. One isincluded in ../qnx

• nm

  This is used (optionally) by configure to listthe contents of libraries. I will generatea cover function on the fly in the UU directory.

• cpp

  Configure and perl need a way to invoke a Cpreprocessor. I have created a simple coverfor cc which does the right thing. Without this,Configure will create its own wrapper which works,but it doesn't handle some of the command line argumentsthat perl will throw at it.

• make

  You really need GNU make to compile this. GNU makeships by default with QNX 4.23, but you can get itfrom quics for earlier versions.

Outstanding Issues with Perl on QNX4

There is no support for dynamically linked libraries in QNX4.

If you wish to compile with the Socket extension, you needto have the TCP/IP toolkit, and you need to make sure that-lsocket locates the correct copy of socket3r.lib. Bewarethat the Watcom compiler ships with a stub version ofsocket3r.lib which has very little functionality. Alsobeware the order in which wlink searches directories forlibraries. You may have /usr/lib/socket3r.lib pointing tothe correct library, but wlink may pick up/usr/watcom/10.6/usr/lib/socket3r.lib instead. Make surethey both point to the correct library, that is,/usr/tcptk/current/usr/lib/socket3r.lib.

The following tests may report errors under QNX4:

dist/Cwd/Cwd.t will complain if `pwd` and cwd don't givethe same results. cwd calls `fullpath -t`, so if youcd `fullpath -t` before running the test, it willpass.

lib/File/Find/taint.t will complain if '.' is in yourPATH. The PATH test is triggered because cwd calls`fullpath -t`.

ext/IO/lib/IO/t/io_sock.t: Subtests 14 and 22 are skipped due tothe fact that the functionality to read back the non-blockingstatus of a socket is not implemented in QNX's TCP/IP. This hasbeen reported to QNX and it may work with later versions ofTCP/IP.

t/io/tell.t: Subtest 27 is failing. We are still investigating.

QNX auxiliary files

The files in the "qnx" directory are:

• qnx/ar

  A script that emulates the standard unix archive (aka library)utility. Under Watcom 10.6, ar is linked to wlib and provides theexpected interface. With Watcom 9.5, a cover function isrequired. This one is fairly crude but has proved adequate forcompiling perl.

• qnx/cpp

  A script that provides C preprocessing functionality. Configure cangenerate a similar cover, but it doesn't handle all the command-lineoptions that perl throws at it. This might be reasonably placed in/usr/local/bin.

Outstanding issues with perl under QNX6

The following tests are still failing for Perl 5.8.1 under QNX 6.2.0:

  op/sprintf.........................FAILED at test 91
 
  lib/Benchmark......................FAILED at test 26
 

This is due to a bug in the C library's printf routine.printf("'%e'", 0. ) produces '0.000000e+0', but ANSI requires'0.000000e+00'. QNX has acknowledged the bug.

AUTHOR

Norton T. Allen ([email protected])