This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
driver/10707: c++ linking impossible when -V specified
- From: gawrilow at math dot tu-berlin dot de
- To: gcc-gnats at gcc dot gnu dot org
- Date: 9 May 2003 16:03:03 -0000
- Subject: driver/10707: c++ linking impossible when -V specified
- Reply-to: gawrilow at math dot tu-berlin dot de
>Number: 10707
>Category: driver
>Synopsis: c++ linking impossible when -V specified
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri May 09 16:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Ewgenij Gawrilow
>Release: 3.3, 3.4 (snapshots)
>Organization:
>Environment:
gcc version 3.3 20030506 (prerelease); gcc version 3.4 20030509 (experimental); platform-independent
>Description:
If g++ is called with -V option and the only input files are objects and libraries, then the alternative driver called in chain cannot guess the language any more, forgets to put libstdc++ in the collect2 call, and the linker fails.
>How-To-Repeat:
Take a little C++ (Hello, world!) program, compile and link it separately, specifying the -V option in both commands.
>Fix:
Probably, the installation script could create an extra hardlink 'machine-g++-version'; the driver could then insert its basename into the execvp() first argument instead of fixed '-gcc-'. Or give along a -x option depending on the own basename.
>Release-Note:
>Audit-Trail:
>Unformatted: