From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>
Subject: [PATCH, doc]: Fix "POD document had syntax errors at /usr/bin/pod2man line 69." error
Date: Sun, 18 May 2014 09:10:00 -0000 [thread overview]
Message-ID: <CAFULd4a6t2SqfRkByT6-Hr4_7q_wEAd-ahxXVNFbpENcBW1BYg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hello!
Attached patch fixes following errors in .pod document sources:
gfdl.pod around line 53: Expected text after =item, not a number
gfdl.pod around line 147: Expected text after =item, not a number
gfdl.pod around line 165: Expected text after =item, not a number
gfdl.pod around line 205: Expected text after =item, not a number
gfdl.pod around line 357: Expected text after =item, not a number
gfdl.pod around line 384: Expected text after =item, not a number
gfdl.pod around line 400: Expected text after =item, not a number
gfdl.pod around line 422: Expected text after =item, not a number
gfdl.pod around line 445: Expected text after =item, not a number
gfdl.pod around line 475: Expected text after =item, not a number
gfdl.pod around line 499: Expected text after =item, not a number
POD document had syntax errors at /usr/bin/pod2man line 69.
gmake[3]: [doc/gfdl.7] Error 1 (ignored)
As suggested in the fix for a similar problem [1], the solution is to
put "Z<>" in the "=item" argument string.
2014-05-18 Uros Bizjak <ubizjak@gmail.com>
* texi2pod.pl: Force .pod file to not be a numbered list.
The fix was tested by bootstrapping on Fedora20 x86_64-pc-linux-gnu,
and also comparing previous .man and .html files with new ones. They
were bit-exact.
OK for mainline and 4.9?
[1] http://comments.gmane.org/gmane.network.inn/9841
Uros.
[-- Attachment #2: c.diff.txt --]
[-- Type: text/plain, Size: 581 bytes --]
Index: texi2pod.pl
===================================================================
--- texi2pod.pl (revision 210579)
+++ texi2pod.pl (working copy)
@@ -1,6 +1,6 @@
#! /usr/bin/perl -w
-# Copyright (C) 1999, 2000, 2001, 2003, 2010 Free Software Foundation, Inc.
+# Copyright (C) 1999-2014 Free Software Foundation, Inc.
# This file is part of GCC.
@@ -337,7 +337,7 @@
$_ = "\n=item $1\n";
}
} else {
- $_ = "\n=item $ic\n";
+ $_ = "\n=item Z\<\>$ic\n";
$ic =~ y/A-Ya-y/B-Zb-z/;
$ic =~ s/(\d+)/$1 + 1/eg;
}
next reply other threads:[~2014-05-18 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 9:10 Uros Bizjak [this message]
2014-05-24 6:40 ` Uros Bizjak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFULd4a6t2SqfRkByT6-Hr4_7q_wEAd-ahxXVNFbpENcBW1BYg@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).