public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/41596]  New: handling of library-related options by g++spec.c causes a failure when generating pch.
Date: Mon, 05 Oct 2009 20:18:00 -0000	[thread overview]
Message-ID: <bug-41596-17110@http.gcc.gnu.org/bugzilla/> (raw)

The recognition of any library-related option in g++-spec.c causes the
insertion of  "-lstdc++".  This causes link to be invoked when trying to
generate PCH, which then fails.  This bit me when trying to run the testsuite
with /-static-libstdc++

The behavior here appears to differ from gcc where one can put "-static-libgcc"
on the CL and the link phase is not invoked for PCH-generation.


-- 
           Summary: handling of library-related options by g++spec.c causes
                    a failure when generating pch.
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: developer at sandoe-acoustics dot co dot uk
 GCC build triplet: *-*-*
  GCC host triplet: *-*-*
GCC target triplet: *-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41596


             reply	other threads:[~2009-10-05 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 20:18 developer at sandoe-acoustics dot co dot uk [this message]
2009-10-05 20:26 ` [Bug c++/41596] " developer at sandoe-acoustics dot co dot uk
2009-12-17 19:52 ` developer at sandoe-acoustics dot co dot uk
2009-12-17 19:54 ` developer at sandoe-acoustics dot co dot uk
2009-12-17 19:58 ` davek at gcc dot gnu dot org

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=bug-41596-17110@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).