| 1 |
.\" -*- mode: troff; coding: utf-8 -*- |
| 2 |
.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45) |
| 3 |
.\" |
| 4 |
.\" Standard preamble: |
| 5 |
.\" ======================================================================== |
| 6 |
.de Sp \" Vertical space (when we can't use .PP) |
| 7 |
.if t .sp .5v |
| 8 |
.if n .sp |
| 9 |
.. |
| 10 |
.de Vb \" Begin verbatim text |
| 11 |
.ft CW |
| 12 |
.nf |
| 13 |
.ne \\$1 |
| 14 |
.. |
| 15 |
.de Ve \" End verbatim text |
| 16 |
.ft R |
| 17 |
.fi |
| 18 |
.. |
| 19 |
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. |
| 20 |
.ie n \{\ |
| 21 |
. ds C` "" |
| 22 |
. ds C' "" |
| 23 |
'br\} |
| 24 |
.el\{\ |
| 25 |
. ds C` |
| 26 |
. ds C' |
| 27 |
'br\} |
| 28 |
.\" |
| 29 |
.\" Escape single quotes in literal strings from groff's Unicode transform. |
| 30 |
.ie \n(.g .ds Aq \(aq |
| 31 |
.el .ds Aq ' |
| 32 |
.\" |
| 33 |
.\" If the F register is >0, we'll generate index entries on stderr for |
| 34 |
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
| 35 |
.\" entries marked with X<> in POD. Of course, you'll have to process the |
| 36 |
.\" output yourself in some meaningful fashion. |
| 37 |
.\" |
| 38 |
.\" Avoid warning from groff about undefined register 'F'. |
| 39 |
.de IX |
| 40 |
.. |
| 41 |
.nr rF 0 |
| 42 |
.if \n(.g .if rF .nr rF 1 |
| 43 |
.if (\n(rF:(\n(.g==0)) \{\ |
| 44 |
. if \nF \{\ |
| 45 |
. de IX |
| 46 |
. tm Index:\\$1\t\\n%\t"\\$2" |
| 47 |
.. |
| 48 |
. if !\nF==2 \{\ |
| 49 |
. nr % 0 |
| 50 |
. nr F 2 |
| 51 |
. \} |
| 52 |
. \} |
| 53 |
.\} |
| 54 |
.rr rF |
| 55 |
.\" ======================================================================== |
| 56 |
.\" |
| 57 |
.IX Title "PERLQNX 1" |
| 58 |
.TH PERLQNX 1 2025-11-16 "perl v5.40.1" "Perl Programmers Reference Guide" |
| 59 |
.\" For nroff, turn off justification. Always turn off hyphenation; it makes |
| 60 |
.\" way too many mistakes in technical documents. |
| 61 |
.if n .ad l |
| 62 |
.nh |
| 63 |
.SH NAME |
| 64 |
perlqnx \- Perl version 5 on QNX |
| 65 |
.SH DESCRIPTION |
| 66 |
.IX Header "DESCRIPTION" |
| 67 |
As of perl5.7.2 all tests pass under: |
| 68 |
.PP |
| 69 |
.Vb 3 |
| 70 |
\& QNX 4.24G |
| 71 |
\& Watcom 10.6 with Beta/970211.wcc.update.tar.F |
| 72 |
\& socket3r.lib Nov21 1996. |
| 73 |
.Ve |
| 74 |
.PP |
| 75 |
As of perl5.8.1 there is at least one test still failing. |
| 76 |
.PP |
| 77 |
Some tests may complain under known circumstances. |
| 78 |
.PP |
| 79 |
See below and hints/qnx.sh for more information. |
| 80 |
.PP |
| 81 |
Under QNX 6.2.0 there are still a few tests which fail. |
| 82 |
See below and hints/qnx.sh for more information. |
| 83 |
.SS "Required Software for Compiling Perl on QNX4" |
| 84 |
.IX Subsection "Required Software for Compiling Perl on QNX4" |
| 85 |
As with many unix ports, this one depends on a few "standard" |
| 86 |
unix utilities which are not necessarily standard for QNX4. |
| 87 |
.IP /bin/sh 4 |
| 88 |
.IX Item "/bin/sh" |
| 89 |
This is used heavily by Configure and then by |
| 90 |
perl itself. QNX4's version is fine, but Configure |
| 91 |
will choke on the 16\-bit version, so if you are |
| 92 |
running QNX 4.22, link /bin/sh to /bin32/ksh |
| 93 |
.IP ar 4 |
| 94 |
.IX Item "ar" |
| 95 |
This is the standard unix library builder. |
| 96 |
We use wlib. With Watcom 10.6, when wlib is |
| 97 |
linked as "ar", it behaves like ar and all is |
| 98 |
fine. Under 9.5, a cover is required. One is |
| 99 |
included in ../qnx |
| 100 |
.IP nm 4 |
| 101 |
.IX Item "nm" |
| 102 |
This is used (optionally) by configure to list |
| 103 |
the contents of libraries. I will generate |
| 104 |
a cover function on the fly in the UU directory. |
| 105 |
.IP cpp 4 |
| 106 |
.IX Item "cpp" |
| 107 |
Configure and perl need a way to invoke a C |
| 108 |
preprocessor. I have created a simple cover |
| 109 |
for cc which does the right thing. Without this, |
| 110 |
Configure will create its own wrapper which works, |
| 111 |
but it doesn't handle some of the command line arguments |
| 112 |
that perl will throw at it. |
| 113 |
.IP make 4 |
| 114 |
.IX Item "make" |
| 115 |
You really need GNU make to compile this. GNU make |
| 116 |
ships by default with QNX 4.23, but you can get it |
| 117 |
from quics for earlier versions. |
| 118 |
.SS "Outstanding Issues with Perl on QNX4" |
| 119 |
.IX Subsection "Outstanding Issues with Perl on QNX4" |
| 120 |
There is no support for dynamically linked libraries in QNX4. |
| 121 |
.PP |
| 122 |
If you wish to compile with the Socket extension, you need |
| 123 |
to have the TCP/IP toolkit, and you need to make sure that |
| 124 |
\&\-lsocket locates the correct copy of socket3r.lib. Beware |
| 125 |
that the Watcom compiler ships with a stub version of |
| 126 |
socket3r.lib which has very little functionality. Also |
| 127 |
beware the order in which wlink searches directories for |
| 128 |
libraries. You may have /usr/lib/socket3r.lib pointing to |
| 129 |
the correct library, but wlink may pick up |
| 130 |
/usr/watcom/10.6/usr/lib/socket3r.lib instead. Make sure |
| 131 |
they both point to the correct library, that is, |
| 132 |
/usr/tcptk/current/usr/lib/socket3r.lib. |
| 133 |
.PP |
| 134 |
The following tests may report errors under QNX4: |
| 135 |
.PP |
| 136 |
dist/Cwd/Cwd.t will complain if `pwd` and cwd don't give |
| 137 |
the same results. cwd calls `fullpath \-t`, so if you |
| 138 |
cd `fullpath \-t` before running the test, it will |
| 139 |
pass. |
| 140 |
.PP |
| 141 |
lib/File/Find/taint.t will complain if '.' is in your |
| 142 |
PATH. The PATH test is triggered because cwd calls |
| 143 |
`fullpath \-t`. |
| 144 |
.PP |
| 145 |
ext/IO/lib/IO/t/io_sock.t: Subtests 14 and 22 are skipped due to |
| 146 |
the fact that the functionality to read back the non-blocking |
| 147 |
status of a socket is not implemented in QNX's TCP/IP. This has |
| 148 |
been reported to QNX and it may work with later versions of |
| 149 |
TCP/IP. |
| 150 |
.PP |
| 151 |
t/io/tell.t: Subtest 27 is failing. We are still investigating. |
| 152 |
.SS "QNX auxiliary files" |
| 153 |
.IX Subsection "QNX auxiliary files" |
| 154 |
The files in the "qnx" directory are: |
| 155 |
.IP qnx/ar 4 |
| 156 |
.IX Item "qnx/ar" |
| 157 |
A script that emulates the standard unix archive (aka library) |
| 158 |
utility. Under Watcom 10.6, ar is linked to wlib and provides the |
| 159 |
expected interface. With Watcom 9.5, a cover function is |
| 160 |
required. This one is fairly crude but has proved adequate for |
| 161 |
compiling perl. |
| 162 |
.IP qnx/cpp 4 |
| 163 |
.IX Item "qnx/cpp" |
| 164 |
A script that provides C preprocessing functionality. Configure can |
| 165 |
generate a similar cover, but it doesn't handle all the command-line |
| 166 |
options that perl throws at it. This might be reasonably placed in |
| 167 |
/usr/local/bin. |
| 168 |
.SS "Outstanding issues with perl under QNX6" |
| 169 |
.IX Subsection "Outstanding issues with perl under QNX6" |
| 170 |
The following tests are still failing for Perl 5.8.1 under QNX 6.2.0: |
| 171 |
.PP |
| 172 |
.Vb 2 |
| 173 |
\& op/sprintf.........................FAILED at test 91 |
| 174 |
\& lib/Benchmark......................FAILED at test 26 |
| 175 |
.Ve |
| 176 |
.PP |
| 177 |
This is due to a bug in the C library's printf routine. |
| 178 |
printf("'%e'", 0. ) produces '0.000000e+0', but ANSI requires |
| 179 |
\&'0.000000e+00'. QNX has acknowledged the bug. |
| 180 |
.SS Cross-compilation |
| 181 |
.IX Subsection "Cross-compilation" |
| 182 |
Perl supports cross-compiling to QNX NTO through the |
| 183 |
Native Development Kit (NDK) for the Blackberry 10. This means that you |
| 184 |
can cross-compile for both ARM and x86 versions of the platform. |
| 185 |
.PP |
| 186 |
\fISetting up a cross-compilation environment\fR |
| 187 |
.IX Subsection "Setting up a cross-compilation environment" |
| 188 |
.PP |
| 189 |
You can download the NDK from |
| 190 |
<http://developer.blackberry.com/native/downloads/>. |
| 191 |
.PP |
| 192 |
See |
| 193 |
<http://developer.blackberry.com/native/documentation/cascades/getting_started/setting_up.html> |
| 194 |
for instructions to set up your device prior to attempting anything else. |
| 195 |
.PP |
| 196 |
Once you've installed the NDK and set up your device, all that's |
| 197 |
left to do is setting up the device and the cross-compilation |
| 198 |
environment. Blackberry provides a script, \f(CW\*(C`bbndk\-env.sh\*(C'\fR (occasionally |
| 199 |
named something like \f(CW\*(C`bbndk\-env_10_1_0_4828.sh\*(C'\fR) which can be used |
| 200 |
to do this. However, there's a bit of a snag that we have to work through: |
| 201 |
The script modifies PATH so that 'gcc' or 'ar' point to their |
| 202 |
cross-compilation equivalents, which screws over the build process. |
| 203 |
.PP |
| 204 |
So instead you'll want to do something like this: |
| 205 |
.PP |
| 206 |
.Vb 3 |
| 207 |
\& $ orig_path=$PATH |
| 208 |
\& $ source $location_of_bbndk/bbndk\-env*.sh |
| 209 |
\& $ export PATH="$orig_path:$PATH" |
| 210 |
.Ve |
| 211 |
.PP |
| 212 |
Besides putting the cross-compiler and the rest of the toolchain in your |
| 213 |
PATH, this will also provide the QNX_TARGET variable, which |
| 214 |
we will pass to Configure through \-Dsysroot. |
| 215 |
.PP |
| 216 |
\fIPreparing the target system\fR |
| 217 |
.IX Subsection "Preparing the target system" |
| 218 |
.PP |
| 219 |
It's quite possible that the target system doesn't have a readily |
| 220 |
available /tmp, so it's generally safer to do something like this: |
| 221 |
.PP |
| 222 |
.Vb 3 |
| 223 |
\& $ ssh $TARGETUSER@$TARGETHOST \*(Aqrm \-rf perl; mkdir perl; mkdir perl/tmp\*(Aq |
| 224 |
\& $ export TARGETDIR=\`ssh $TARGETUSER@$TARGETHOST pwd\`/perl |
| 225 |
\& $ export TARGETENV="export TMPDIR=$TARGETDIR/tmp; " |
| 226 |
.Ve |
| 227 |
.PP |
| 228 |
Later on, we'll pass this to Configure through \-Dtargetenv |
| 229 |
.PP |
| 230 |
\fICalling Configure\fR |
| 231 |
.IX Subsection "Calling Configure" |
| 232 |
.PP |
| 233 |
If you are targetting an ARM device \-\- which currently includes the vast |
| 234 |
majority of phones and tablets \-\- you'll want to pass |
| 235 |
\&\-Dcc=arm\-unknown\-nto\-qnx8.0.0eabi\-gcc to Configure. Alternatively, if you |
| 236 |
are targetting an x86 device, or using the simulator provided with the NDK, |
| 237 |
you should specify \-Dcc=ntox86\-gcc instead. |
| 238 |
.PP |
| 239 |
A sample Configure invocation looks something like this: |
| 240 |
.PP |
| 241 |
.Vb 6 |
| 242 |
\& ./Configure \-des \-Dusecrosscompile \e |
| 243 |
\& \-Dsysroot=$QNX_TARGET \e |
| 244 |
\& \-Dtargetdir=$TARGETDIR \e |
| 245 |
\& \-Dtargetenv="$TARGETENV" \e |
| 246 |
\& \-Dcc=ntox86\-gcc \e |
| 247 |
\& \-Dtarghost=... # Usual cross\-compilation options |
| 248 |
.Ve |
| 249 |
.SH AUTHOR |
| 250 |
.IX Header "AUTHOR" |
| 251 |
Norton T. Allen ([email protected]) |