Debian Codegraph @

upstream/opensuse-tumbleweed/man1/perlqnx.1

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