public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/62224] [4.9 Regression] Possible regression in gcc-4.9-20140820
Date: Wed, 03 Sep 2014 07:44:00 -0000	[thread overview]
Message-ID: <bug-62224-4-xk47mnsOVO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62224-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62224

--- Comment #13 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Chris Clayton from comment #12)
> Sorry, you'll have to stick with me here while a figure out what that means.
> 
> I think you are saying that prior to r214208, the symbols definedMacros()
> and headerPaths() were present but effectively no-ops. Post r214208 they now
> "contain" operations including calls to ensureUpdated().
> 
> Given that the symbol for ensureUpdated() appears to be present in
> libCppTools.so (along with the symbols for its two post-r214208 callers),
> does that suggest a problem with the linker, which is /usr/bin/ld from the
> latest version (2.24) of binutils?

No. This has nothing to do with libCppTools.so. As I wrote before the 
build system of qt-creator must be changed to provide the missing symbol
by simply adding cppmodelmanager.o to the libCppEditor.so link command.


  parent reply	other threads:[~2014-09-03  7:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  7:46 [Bug c++/62224] New: " chris2553 at googlemail dot com
2014-08-22  7:50 ` [Bug c++/62224] " chris2553 at googlemail dot com
2014-08-26 10:58 ` [Bug c++/62224] [4.9 Regression] " rguenth at gcc dot gnu.org
2014-08-28  7:55 ` chris2553 at googlemail dot com
2014-09-01  9:23 ` jakub at gcc dot gnu.org
2014-09-01 21:32 ` chris2553 at googlemail dot com
2014-09-02 17:57 ` jason at gcc dot gnu.org
2014-09-02 19:09 ` chris2553 at googlemail dot com
2014-09-02 20:20 ` trippels at gcc dot gnu.org
2014-09-02 20:55 ` chris2553 at googlemail dot com
2014-09-02 21:22 ` trippels at gcc dot gnu.org
2014-09-03  6:57 ` trippels at gcc dot gnu.org
2014-09-03  7:33 ` chris2553 at googlemail dot com
2014-09-03  7:44 ` trippels at gcc dot gnu.org [this message]
2014-09-03  9:26 ` trippels at gcc dot gnu.org
2014-09-09 11:58 ` jason at gcc dot gnu.org
2014-09-09 12:13 ` trippels at gcc dot gnu.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-62224-4-xk47mnsOVO@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).