public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/7817: [3.2/3.3 regression] Link to gcc man page in g++ man page incorrect
Date: Wed, 12 Mar 2003 07:16:00 -0000 [thread overview]
Message-ID: <20030312071600.24013.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/7817; it has been noted by GNATS.
From: Alexandre Oliva <aoliva@redhat.com>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: gcc-gnats@gcc.gnu.org, backes@rhrk.uni-kl.de, gcc-bugs@gcc.gnu.org,
nobody@gcc.gnu.org
Subject: Re: bootstrap/7817: [3.2/3.3 regression] Link to gcc man page in g++ man page incorrect
Date: 12 Mar 2003 04:05:33 -0300
On Mar 12, 2003, Steven Bosscher <s.bosscher@student.tudelft.nl> wrote:
> Alexandre, does your patch "get g++ man page to point to the right gcc
> man page" (http://gcc.gnu.org/ml/gcc-patches/2003-03/msg01043.html)
> fix this high priority PR? If so, can the patch go on the 3.3 branch
> too?
Hmm... I'm afraid not. The bug report describes a different problem,
that I wasn't even aware of. I can't duplicate the problem on my
GNU/Linux box, and IRIX 6.5's man just says it fails to support `.so',
and since I'm mostly clueless as far as man-pages go, I'm not sure
whether .so is supposed to list a pathname relative to the location of
the file that contains the directive or the pathname is searched in
the MANPATH. Current behavior seems to indicate the latter, but the
bug report seems to imply this is not portable. Installing the gcc
man-page as g++.1 is probably as good a solution as any. I don't
quite like the idea of installing a soft-link because soft links are
not that portable, and the fallback on systems that don't support it
is copying, which may not do the right think if g++.1 is installed
before gcc.1.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next reply other threads:[~2003-03-12 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 7:16 Alexandre Oliva [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 6:56 Steven Bosscher
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=20030312071600.24013.qmail@sources.redhat.com \
--to=aoliva@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).