summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--README.os28
-rw-r--r--t/porting/known_pod_issues.dat3
2 files changed, 6 insertions, 5 deletions
diff --git a/README.os2 b/README.os2
index b5f327aa3f..275ce732a0 100644
--- a/README.os2
+++ b/README.os2
@@ -196,8 +196,8 @@ Cf. L</Prerequisites>.
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
@@ -300,7 +300,7 @@ with
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 C<L</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>:
@@ -2434,7 +2434,7 @@ would not.
=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
diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat
index aea5a91ba1..291e022fa8 100644
--- a/t/porting/known_pod_issues.dat
+++ b/t/porting/known_pod_issues.dat
@@ -106,6 +106,7 @@ Devel::Spy
dirfd(3)
dirname(1)
dup(2)
+emxbind(1)
Encode::Detect
Encode::Locale
Eval::WithLexicals
@@ -398,7 +399,7 @@ pod/perlhist.pod Verbatim line length including indents exceeds 78 by 1
pod/perlinterp.pod ? Should you be using L<...> instead of 1
pod/perlmacosx.pod Verbatim line length including indents exceeds 78 by 3
pod/perlmroapi.pod ? Should you be using L<...> instead of 1
-pod/perlos2.pod ? Should you be using L<...> instead of 2
+pod/perlos2.pod ? Should you be using L<...> instead of 1
pod/perlos2.pod Verbatim line length including indents exceeds 78 by 5
pod/perlos390.pod Verbatim line length including indents exceeds 78 by 1
pod/perlperf.pod Verbatim line length including indents exceeds 78 by -1