This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/11146] Bad characters in cpp.1, gcc.1 man pages
- From: "jsm28 at cam dot ac dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Jun 2003 08:57:51 -0000
- Subject: [Bug other/11146] Bad characters in cpp.1, gcc.1 man pages
- References: <20030611031019.11146.drk@sgi.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11146
------- Additional Comments From jsm28@cam.ac.uk 2003-06-11 08:57 -------
Subject: Re: Bad characters in cpp.1, gcc.1 man pages
On Wed, 11 Jun 2003, drk@sgi.com wrote:
> Created an attachment (id=4197)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=4197&action=view)
> --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=4197&action=view)
> Proposed fix
>
> Note that patch doesn't actually process files containing
> NULLs properly; you'll have to apply this by hand.
Patching generated files is not a suitable fix. Someone (Zack is the most
expert in this area) will need to determine which generation stage
(texi2pod.pl or pod2man) is introducing these characters and either fix
texi2pod.pl or fix pod2man and adjust the version requirements on it.
Problems with what patch handles are only relevant insofar as this might
cause problems for people applying the 3.3.1 diff if the problem is fixed
for 3.3.1, if patch 2.5.4 (the version we recommend, because some earlier
versions are known to have problems with binary diffs) won't handle these
characters properly.