From 90c87169fab88b312f4e459fd36b807eee55ed18 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sat, 16 Jul 2011 13:46:48 -0600 Subject: perlos2: Fix some link issues The link to emxbind needs some explanation. Perhaps on an os/2 system, this command exists, but any link to it is using cpan's search which doesn't find it --- README.os2 | 5 ++--- t/porting/known_pod_issues.dat | 6 +++--- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/README.os2 b/README.os2 index 359fc844ab..0425292771 100644 --- a/README.os2 +++ b/README.os2 @@ -196,7 +196,7 @@ Cf. L. EMX runtime is required (may be substituted by RSX). Note that it is possible to make F to run under DOS without any -external support by binding F/F to it, see L. Note +external support by binding F/F to it, see C. Note that under DOS for best results one should use RSX runtime, which has much more functions working (like C, C and so on). In fact RSX is required if there is no VCPI present. Note the @@ -1111,7 +1111,7 @@ named accordingly. Fully build and test the Perl distribution. Make sure that no tests are failing with C and C targets; fix the bugs in Perl and the Perl test suite detected by these tests. Make sure that C -make target runs as clean as possible. Check that C +make target runs as clean as possible. Check that F runs fine. =item 2. @@ -2218,7 +2218,6 @@ It is a VIO application. Since Perl processes the C<#!>-line (cf. L, L, -L, L), it should know when a program I. There is some naming convention which allows Perl to distinguish correct lines from wrong ones. The above names are diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat index 12c7be51fa..af25387944 100644 --- a/t/porting/known_pod_issues.dat +++ b/t/porting/known_pod_issues.dat @@ -82,6 +82,7 @@ perllexwarn(1) perlthanks POD2::FR POD2::IT +pod2ipf(1) pod2man(1) Pod::HTML2Pod Pod::Plainer @@ -103,6 +104,7 @@ Shell Shell::Command sock_init(3) socketpair(3) +SOM splain sprintf(3) stat(2) @@ -262,9 +264,7 @@ pod/perlmroapi.pod ? Should you be using L<...> instead of 1 pod/perlnetware.pod Verbatim line length including indents exceeds 80 by 4 pod/perlnewmod.pod Verbatim line length including indents exceeds 80 by 1 pod/perlop.pod Verbatim line length including indents exceeds 80 by 30 -pod/perlos2.pod ? Should you be using F<...> or maybe L<...> instead of 1 -pod/perlos2.pod ? Should you be using L<...> instead of 1 -pod/perlos2.pod Apparent broken link 4 +pod/perlos2.pod ? Should you be using L<...> instead of 2 pod/perlos2.pod Verbatim line length including indents exceeds 80 by 22 pod/perlos390.pod Verbatim line length including indents exceeds 80 by 11 pod/perlpacktut.pod Verbatim line length including indents exceeds 80 by 6 -- cgit v1.2.1