Re: help (fwd)

[PRASHANT SRINIVASAN <prash at gnu dot org>]

 Should the link
to http://www.gnu.org/software/gcc/onlinedocs/gcov_toc.html on the page
http://www.gnu.org/software/gcc/onlinedocs/ actually point to
http://gcc.gnu.org/onlinedocs/gcov_toc.html ?

The current link points to an empty webpage generated on 31st march by
texi2html; but the one which works, was created on 15th march by
texi2html.

thanks,
 Prashant.

---------- Forwarded message ----------
Date: Tue, 28 Mar 2000 21:56:43 -0500
From: Bradley M. Kuhn <gnu@gnu.org>
To: "[iso-8859-1] ϲ»¶Ë¼¿¼" <wangchaosh@263.net>
Cc: webmasters@gnu.org
Subject: Re: help

ϲ»¶Ë¼¿¼ wrote:

> why the GCOV MANUAL is
> empty?(http://www.gnu.org/software/gcc/onlinedocs/gcov_toc.html) and i
> can't find the GCOV tool any where.  Could you give me an answer about it?

It could be that this software is still under development, and not yet
documented nor in the canonical release.

The best thing to do is to ask <help-gcc@gnu.org>.  The people there deal
with GCC on a daily basis.

In the meantime, I will ask our WWW masters to remove the dead link.


Most gnu mailing lists can be subscribed to by writing to 
foo-request@gnu.org (where "foo" is the name of the list you are
trying subscribe to) with "subscribe" in the body of the message.

You can subscribe an arbitrary address (as opposed to the one you
are mailing from) by putting "subscribe foo@whatever.com" in the body
of the message.  (Where "foo@whatever.com" is the address you want
to get the mail at.)


* General Information about help-* lists

These lists (and their newsgroups) exist for anyone to ask questions
about the GNU software that the list deals with.  The lists are read by
people who are willing to take the time to help other users.

When you answer the questions that people ask on the help-* lists, keep
in mind that you shouldn't answer by promoting a proprietary program as
a solution.  The only real solutions are the ones all the readers can
share.

If a program crashes, or if you build it following the standard
procedure on a system on which it is supposed to work and it does not
work at all, or if an command does not behave as it is documented to
behave, this is a bug.  Don't send bug reports to a help-* list; mail
them to the bug-* list instead.


* help-gcc-request@gnu.org to subscribe to help-gcc
** gnUSENET newsgroup: gnu.gcc.help
** Send contributions to: help-gcc@gnu.org

This list is the place for users and installers of the GNU C Compiler to
ask for help.

If gcc crashes, or if you build gcc following the standard procedure on
a system which gcc is supposed to work on (see config.sub) and it does
not work at all, or if an command line option does not behave as it is
documented to behave, this is a bug.  Don't send bug reports to help-gcc
(gnu.gcc.help); mail them to bug-gcc@gnu.org instead.