public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "backesærhrk".uni-kl.de@rhrk.uni-kl.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/7816: Install gcc-3.2 man pages
Date: Tue, 03 Sep 2002 01:16:00 -0000	[thread overview]
Message-ID: <200209030815.KAA01060@origin.rhrk.uni-kl.de> (raw)


>Number:         7816
>Category:       c++
>Synopsis:       Wrong installation of man page g++.1
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 03 01:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Joachim Backes
>Release:        3.2
>Organization:
University of Kaiserslautern, Computer Center
>Environment:
System: IRIX64 origin 6.5 04101930 IP27


OS: IRIX 6.5, Hardware Origin 2000
host: mips-sgi-irix6.5
build: mips-sgi-irix6.5
target: mips-sgi-irix6.5
configured with: ../configure 
>Description:
Hi,

I have built gcc-3.2 for IRIX 6.5 sucessfully.

There is one small bug in the install procedure: after
the man pages are installed, then the man page for g++
is not correct (at least for IRIX 6.5): g++.1 is
a very small file with the contents:

        .so man1/gcc.1

So, gcc.1 will not be found because is situated in ./gcc.1,
but not in man1/gcc.1 because man1 is not contained in man1.
Better would be:

        ln -s gcc.1 g++.1

in the man1 directory itself.
	
>How-To-Repeat:
>Fix:
Make link: ln -s gcc.1 g++.1 in the man1 directory

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-09-03  8:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200209030815.KAA01060@origin.rhrk.uni-kl.de \
    --to=gcc-gnats@gcc.gnu.org \
    --cc=backes@rhrk.uni-kl.de \
    /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).