public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: lrtaylor@micron.com
To: <gcc-help@gcc.gnu.org>
Subject: RE: command line help
Date: Wed, 08 Dec 2004 18:56:00 -0000	[thread overview]
Message-ID: <363801FFD7B74240A329CEC3F7FE4CC40215DC99@ntxboimbx07.micron.com> (raw)

If you're on Linux or some flavor of UNIX, you might also try looking at
the man page.

	man gcc

Or take a look at the online documentation for GCC.  Go to
http://gcc.gnu.org/ and click on the Manual link under Documentation in
the menu on the left.

You might also seriously consider going to a local bookstore and getting
a book about software development on Linux or something similar.
Another poster on the list has even written an introductory book about
using GCC.  You might take a look at that:

http://www.network-theory.co.uk/gcc/intro/

Thanks,
Lyle


-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Brian Rose
Sent: Wednesday, December 08, 2004 11:49 AM
To: gcc-help@gcc.gnu.org
Subject: Re: command line help

tinettim@gdls.com wrote:

> At the command line I can type help to get a list of topics but they
scroll
> of the screen so I can't see them all and I can't find their
explanations
> on your web site. What command do I use to get it to compile? Source?
What
> directory should I be in when I compile and what subdirectories should
I
> have.
> 

gcc --help | more


Simple C program in hello.c would be compiled into an executable called 
'program' like this....

gcc -o program hello.c




-- 

Brian

             reply	other threads:[~2004-12-08 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 18:56 lrtaylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-08 18:20 tinettim
2004-12-08 18:49 ` Brian Rose

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=363801FFD7B74240A329CEC3F7FE4CC40215DC99@ntxboimbx07.micron.com \
    --to=lrtaylor@micron.com \
    --cc=gcc-help@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).