public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Smith <paul@mad-scientist.net>
To: Jim Anderson <jjanders@ptd.net>, gcc@gcc.gnu.org
Subject: Re: Good grief Charlie Brown
Date: Tue, 13 Dec 2022 11:41:07 -0500	[thread overview]
Message-ID: <b461cdbcfeba409fd2662bb8e9166aa9576014fa.camel@mad-scientist.net> (raw)
In-Reply-To: <cbdc7e3c-efeb-bc56-2f88-047ea50ffdf4@ptd.net>

On Tue, 2022-12-13 at 11:28 -0500, Jim Anderson via Gcc wrote:
> 1) I could not find any place to download the man page. I lost my 
> internet connect and I have not man page :(

You didn't say what platform you're working on, nor how you obtained
the GCC that you are using, but recall that the GCC team doesn't
publish already-built binary packages.  If you built your own version
of GCC from source, then all the documentation was contained with the
source code.

If you didn't build it yourself and instead installed a pre-built
version, then you need to discuss this with the group that provided
that pre-built version: the GCC development team can't help.  Every
binary package of GCC I've ever heard of comes with at least the man
page (some distributions bundle the full documentation separately from
the compiler but they all include the man page with the compiler).

Did you try just running "man gcc" (assuming you are on a POSIX-type
system)?

> 2) How over pervasive gcc has become. It appears to be everything for
> everybody for every environment possible.
> 
> I guess this is a good think, but I personally think not!

I guess if you were one of the "everybody" needing "everything" on
"every" environment, instead of you needing what you need in your
environment, you might think differently!

  reply	other threads:[~2022-12-13 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 16:28 Jim Anderson
2022-12-13 16:41 ` Paul Smith [this message]
2022-12-13 17:35   ` Dave Blanchard
2022-12-13 18:31     ` Paul Smith
2022-12-13 19:16 ` Dave Blanchard
2022-12-13 19:09 Dave Blanchard
2022-12-13 19:20 ` Paul Koning
2022-12-13 19:29   ` Dave Blanchard
2022-12-13 20:35     ` Jonathan Wakely

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=b461cdbcfeba409fd2662bb8e9166aa9576014fa.camel@mad-scientist.net \
    --to=paul@mad-scientist.net \
    --cc=gcc@gcc.gnu.org \
    --cc=jjanders@ptd.net \
    /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).