diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-15 19:43:11 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-15 19:43:11 +0000 |
commit | fc22b3d6507c6745911b9dfcc68f1e665ae13dbc (patch) | |
tree | ce1e3bce06471410239a6f41282e328770aa404a /upstream/debian-unstable/man1/perlos400.1 | |
parent | Initial commit. (diff) | |
download | manpages-l10n-fc22b3d6507c6745911b9dfcc68f1e665ae13dbc.tar.xz manpages-l10n-fc22b3d6507c6745911b9dfcc68f1e665ae13dbc.zip |
Adding upstream version 4.22.0.upstream/4.22.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'upstream/debian-unstable/man1/perlos400.1')
-rw-r--r-- | upstream/debian-unstable/man1/perlos400.1 | 175 |
1 files changed, 175 insertions, 0 deletions
diff --git a/upstream/debian-unstable/man1/perlos400.1 b/upstream/debian-unstable/man1/perlos400.1 new file mode 100644 index 00000000..7ebd5b61 --- /dev/null +++ b/upstream/debian-unstable/man1/perlos400.1 @@ -0,0 +1,175 @@ +.\" -*- mode: troff; coding: utf-8 -*- +.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) +.\" +.\" Standard preamble: +.\" ======================================================================== +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Vb \" Begin verbatim text +.ft CW +.nf +.ne \\$1 +.. +.de Ve \" End verbatim text +.ft R +.fi +.. +.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. +.ie n \{\ +. ds C` "" +. ds C' "" +'br\} +.el\{\ +. ds C` +. ds C' +'br\} +.\" +.\" Escape single quotes in literal strings from groff's Unicode transform. +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" +.\" If the F register is >0, we'll generate index entries on stderr for +.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" entries marked with X<> in POD. Of course, you'll have to process the +.\" output yourself in some meaningful fashion. +.\" +.\" Avoid warning from groff about undefined register 'F'. +.de IX +.. +.nr rF 0 +.if \n(.g .if rF .nr rF 1 +.if (\n(rF:(\n(.g==0)) \{\ +. if \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" +.. +. if !\nF==2 \{\ +. nr % 0 +. nr F 2 +. \} +. \} +.\} +.rr rF +.\" ======================================================================== +.\" +.IX Title "PERLOS400 1" +.TH PERLOS400 1 2024-01-12 "perl v5.38.2" "Perl Programmers Reference Guide" +.\" For nroff, turn off justification. Always turn off hyphenation; it makes +.\" way too many mistakes in technical documents. +.if n .ad l +.nh +.SH NAME +perlos400 \- Perl version 5 on OS/400 +.PP +This document needs to be updated, but we don't know what it should say. +Please submit comments to <https://github.com/Perl/perl5/issues>. +.SH DESCRIPTION +.IX Header "DESCRIPTION" +This document describes various features of IBM's OS/400 operating +system that will affect how Perl version 5 (hereafter just Perl) is +compiled and/or runs. +.PP +By far the easiest way to build Perl for OS/400 is to use the PASE +(Portable Application Solutions Environment), for more information see +<http://www.iseries.ibm.com/developer/factory/pase/index.html> +This environment allows one to use AIX APIs while programming, and it +provides a runtime that allows AIX binaries to execute directly on the +PowerPC iSeries. +.SS "Compiling Perl for OS/400 PASE" +.IX Subsection "Compiling Perl for OS/400 PASE" +The recommended way to build Perl for the OS/400 PASE is to build the +Perl 5 source code (release 5.8.1 or later) under AIX. +.PP +The trick is to give a special parameter to the Configure shell script +when running it on AIX: +.PP +.Vb 1 +\& sh Configure \-DPASE ... +.Ve +.PP +The default installation directory of Perl under PASE is /QOpenSys/perl. +This can be modified if needed with Configure parameter \-Dprefix=/some/dir. +.PP +Starting from OS/400 V5R2 the IBM Visual Age compiler is supported +on OS/400 PASE, so it is possible to build Perl natively on OS/400. +The easier way, however, is to compile in AIX, as just described. +.PP +If you don't want to install the compiled Perl in AIX into /QOpenSys +(for packaging it before copying it to PASE), you can use a Configure +parameter: \-Dinstallprefix=/tmp/QOpenSys/perl. This will cause the +"make install" to install everything into that directory, while the +installed files still think they are (will be) in /QOpenSys/perl. +.PP +If building natively on PASE, please do the build under the /QOpenSys +directory, since Perl is happier when built on a case sensitive filesystem. +.SS "Installing Perl in OS/400 PASE" +.IX Subsection "Installing Perl in OS/400 PASE" +If you are compiling on AIX, simply do a "make install" on the AIX box. +Once the install finishes, tar up the /QOpenSys/perl directory. Transfer +the tarball to the OS/400 using FTP with the following commands: +.PP +.Vb 3 +\& > binary +\& > site namefmt 1 +\& > put perl.tar /QOpenSys +.Ve +.PP +Once you have it on, simply bring up a PASE shell and extract the tarball. +.PP +If you are compiling in PASE, then "make install" is the only thing you +will need to do. +.PP +The default path for perl binary is /QOpenSys/perl/bin/perl. You'll +want to symlink /QOpenSys/usr/bin/perl to this file so you don't have +to modify your path. +.SS "Using Perl in OS/400 PASE" +.IX Subsection "Using Perl in OS/400 PASE" +Perl in PASE may be used in the same manner as you would use Perl on AIX. +.PP +Scripts starting with #!/usr/bin/perl should work if you have +/QOpenSys/usr/bin/perl symlinked to your perl binary. This will not +work if you've done a setuid/setgid or have environment variable +PASE_EXEC_QOPENSYS="N". If you have V5R1, you'll need to get the +latest PTFs to have this feature. Scripts starting with +#!/QOpenSys/perl/bin/perl should always work. +.SS "Known Problems" +.IX Subsection "Known Problems" +When compiling in PASE, there is no "oslevel" command. Therefore, +you may want to create a script called "oslevel" that echoes the +level of AIX that your version of PASE runtime supports. If you're +unsure, consult your documentation or use "4.3.3.0". +.PP +If you have test cases that fail, check for the existence of spool files. +The test case may be trying to use a syscall that is not implemented +in PASE. To avoid the SIGILL, try setting the PASE_SYSCALL_NOSIGILL +environment variable or have a handler for the SIGILL. If you can +compile programs for PASE, run the config script and edit config.sh +when it gives you the option. If you want to remove \fBfchdir()\fR, which +isn't implement in V5R1, simply change the line that says: +.PP +d_fchdir='define' +.PP +to +.PP +d_fchdir='undef' +.PP +and then compile Perl. The places where \fBfchdir()\fR is used have +alternatives for systems that do not have \fBfchdir()\fR available. +.SS "Perl on ILE" +.IX Subsection "Perl on ILE" +There exists a port of Perl to the ILE environment. This port, however, +is based quite an old release of Perl, Perl 5.00502 (August 1998). +(As of July 2002 the latest release of Perl is 5.8.0, and even 5.6.1 +has been out since April 2001.) If you need to run Perl on ILE, though, +you may need this older port: <http://www.cpan.org/ports/#os400> +Note that any Perl release later than 5.00502 has not been ported to ILE. +.PP +If you need to use Perl in the ILE environment, you may want to consider +using \fBQp2RunPase()\fR to call the PASE version of Perl. +.SH AUTHORS +.IX Header "AUTHORS" +Jarkko Hietaniemi <jhi@iki.fi> +Bryan Logan <bryanlog@us.ibm.com> +David Larson <larson1@us.ibm.com> |