+# vim: syntax=pod
+
If you read this file _as_is_, just ignore the funny characters you
see. It is written in the POD format (see perlpod manpage) which is
specially designed to be readable as is.
EMX runtime is required (may be substituted by RSX). Note that
it is possible to make F<perl_.exe> to run under DOS without any
-external support by binding F<emx.exe>/F<rsx.exe> to it, see C<emxbind>. Note
-that under DOS for best results one should use RSX runtime, which
+external support by binding F<emx.exe>/F<rsx.exe> to it, see L<emxbind(1)>.
+Note that under DOS for best results one should use RSX runtime, which
has much more functions working (like C<fork>, C<popen> and so on). In
fact RSX is required if there is no VCPI present. Note the
RSX requires DPMI. Many implementations of DPMI are known to be very
perl ../../blah/foo.cmd arg1 arg2 arg3
(note that the argument C<-my_opts> is taken care of by the C<extproc> line
-in your script, see L</C<extproc> on the first line>).
+in your script, see C<L</extproc>> on the first line).
To understand what the above I<magic> does, read perl docs about C<-S>
switch - see L<perlrun>, and cmdref about C<extproc>:
=back
-=head2 C<``> and pipe-C<open> do not work under DOS.
+=head2 C<``> and pipe-C<open> do not work under DOS
This may a variant of just L</"I cannot run external programs">, or a
deeper problem. Basically: you I<need> RSX (see L</Prerequisites>)
B<NOTE>. Because of a typo the binary installer of 5.00305
would install a variable C<PERL_SHPATH> into F<Config.sys>. Please
-remove this variable and put L</C<PERL_SH_DIR>> instead.
+remove this variable and put C<L</PERL_SH_DIR>> instead.
=head2 Manual binary installation
=item Additional Perl modules
- unzip perl_ste.zip -d f:/perllib/lib/site_perl/5.32.0/
+ unzip perl_ste.zip -d f:/perllib/lib/site_perl/5.39.8/
Same remark as above applies. Additionally, if this directory is not
one of directories on @INC (and @INC is influenced by C<PERLLIB_PREFIX>), you
emximp -o foo.a foo.lib
whichever is appropriate.) Also, make sure that the DLLs for external
-libraries are usable with with executables compiled without C<-Zmtd> options.
+libraries are usable with executables compiled without C<-Zmtd> options.
When you are sure that only a few subdirectories
lead to failures, you may want to add C<-j4> option to C<make> to speed up
to ignore the environment when setting the Perl-library search patch, etc.
If you fill comfortable with I<embedding> interface (see L<perlembed>), such
-things are easy to do repeating the steps outlined in L/<Making
+things are easy to do repeating the steps outlined in L</Making
executables with a custom collection of statically loaded extensions>, and
doing more comprehensive edits to main() of F<perlmain.c>. The people with
little desire to understand Perl can just rename main(), and do necessary
=head1 Build FAQ
-=head2 Some C</> became C<\> in pdksh.
+=head2 Some C</> became C<\> in pdksh
You have a very old pdksh. See L</Prerequisites>.
=head2 Priorities
C<setpriority> and C<getpriority> are not compatible with earlier
-ports by Andreas Kaiser. See C<"setpriority, getpriority">.
+ports by Andreas Kaiser. See L</setpriority, getpriority>.
=head2 DLL name mangling: pre 5.6.2