X-Spam-Check-By:	sourceware.org
Message-ID:	<26b51c320512160920t2f04020xab2f7d297ea118ca@mail.gmail.com>
Date:	Fri, 16 Dec 2005 12:20:41 -0500
From:	Adam Buchbinder <adam DOT buchbinder AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Documentation bug: gcc(1) in gcc-core 3.4.4-1
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id jBGHKptR014653

There is leftover markup from the texinfo source in the manual page
for gcc(1) in the current version. The file is included in the package
gcc-core version 3.4.4-1. Specifically, search for @pxref and @anchor,
which shouldn't be showing up in the output.

Also, the documentation for -print-multi-lib seems to be mangled:

-print-multi-lib
    Print the mapping from multilib directory names to compiler
    switches that enable them.  The directory name is separated from
    the switches by ;, and each switch starts with an @} instead of the
    @samp{-, without spaces between multiple switches.  This is sup-
    posed to ease shell-processing.

The troff source for this part reads as follows.

.IP "\fB\-print\-multi\-lib\fR" 4
.IX Item "-print-multi-lib"
Print the mapping from multilib directory names to compiler switches
that enable them.  The directory name is separated from the switches by
\&\fB;\fR, and each switch starts with an \fB@} instead of the
\&\f(CB AT samp\fB{\-\fR, without spaces between multiple switches.  This
is supposed to
ease shell\-processing.

Should this go upstream to the gcc folks?

Adam Buchbinder

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -