public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gavin Romig-Koch <gavin@cygnus.com>
To: Takuya Kobayashi <tictak@mail.utexas.edu>
Subject: which g++ ?
Date: Mon, 09 Nov 1998 13:30:00 -0000	[thread overview]
Message-ID: <13894.64389.753379.846@cetus.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96LJ1.1b7.981108185436.22540A-100000@resnet-20-70.dorm.utexas.edu>

Takuya Kobayashi writes:
 > 	g++ main.cpp -o main
 > 
 > Which "g++" am I invoking?  Does one override the other?  It seems like
 > a stupid question, but nevertheless I needed to know, so....

Your question isn't stupid, just asked in the wrong forum.  Your question
has more to do with how Unix works, or more specifically how the typical
Unix command line shell works.  I'd strongly recommend a good book on 
Unix (or perhaps there's something online these days).

It is likely that your using Bash as your shell.  If so, you can 
find the answer to your question in the Bash man page, 
type "man bash", under the section entitled "COMMAND EXECUTION",
particularly the use of the PATH shell variable.  Also, if you
are running Bash, the command "type g++" will tell you where
g++ is found.  If you are not running Bash, the above may help
anyway, this behavior is very standard across all unix shells.

Finally, like most GNU tools, g++ supports the --version option:

     g++ --version

will print out the version of g++ that gets run.  If you know the
version of g++ that comes with your version of RedHat, and the
version of g++ that you installed, you can use this to tell what's
actually getting run.

Good luck.

                                           -gavin...


  parent reply	other threads:[~1998-11-09 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-08 20:53 Takuya Kobayashi
1998-11-09  2:35 ` Gerald Pfeifer
1998-11-09 14:34   ` egcs on mipsel? Greg
1998-11-09 13:30 ` Gavin Romig-Koch [this message]
1998-11-12  1:09 ` which g++ ? Martin Kahlert
1998-12-09  7:02 ` siliconjackal

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=13894.64389.753379.846@cetus.cygnus.com \
    --to=gavin@cygnus.com \
    --cc=tictak@mail.utexas.edu \
    /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).