This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/10707] c++ linking impossible when -V specified
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Jun 2003 02:50:49 -0000
- Subject: [Bug driver/10707] c++ linking impossible when -V specified
- References: <20030509160600.10707.gawrilow@math.tu-berlin.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10707
bangerth@dealii.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |minor
------- Additional Comments From bangerth@dealii.org 2003-06-01 02:50 -------
While the PR is certainly valid, -V is not really the recommended way
anymore to use different compilers. It was used, IIRC, in the time
frame of before gcc2.8 or so, and indeed the manual entry for -V
gives revealing clues about when this was useful:
@item -V @var{version}
@opindex V
The argument @var{version} specifies which version of GCC to run.
This is useful when multiple versions are installed. For example,
@var{version} might be @samp{2.0}, meaning to run GCC version 2.0.
@end table
The way to go these days is to install different versions of gcc into
different directories.
I have the feeling that this will some day be "fixed" by obsoleting -V...
W.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.