public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul.scruby at ghco dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/53604] ld reports errors using lto after upgrading from gcc-4.6.2 to gcc-4.7.0
Date: Wed, 13 Jun 2012 11:57:00 -0000	[thread overview]
Message-ID: <bug-53604-4-XyHD4jZe41@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53604-4@http.gcc.gnu.org/bugzilla/>

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

Paul Scruby <paul.scruby at ghco dot co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|DUPLICATE                   |

--- Comment #5 from Paul Scruby <paul.scruby at ghco dot co.uk> 2012-06-13 11:56:53 UTC ---
Thanks Yuri.  I swapped out this function with yours but ld was still unable to
link.  I'm trying linking to my own libraries statically using the lto and the
boost shared libraries.  Linking to one of the other seems to be fine.

I'm not sure if this is the same bug as bug 53572 (gcc4.7.1) or a different
one.  If you can point me in the direction of a gcc4.7.1 release, I'm happy to
test my build to see if this problem has now been resolved.

Thanks again,

Paul


  parent reply	other threads:[~2012-06-13 11:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 15:10 [Bug lto/53604] New: " paul.scruby at ghco dot co.uk
2012-06-07 15:51 ` [Bug lto/53604] " hjl.tools at gmail dot com
2012-06-07 17:14 ` paul.scruby at ghco dot co.uk
2012-06-11 17:04 ` tetra2005 at gmail dot com
2012-06-12 10:42 ` rguenth at gcc dot gnu.org
2012-06-13 11:57 ` paul.scruby at ghco dot co.uk [this message]
2012-06-13 12:30 ` tetra2005 at gmail dot com
2012-06-13 14:29 ` redi at gcc dot gnu.org
2012-06-13 14:34 ` paul.scruby at ghco dot co.uk
2012-06-13 16:44 ` paul.scruby at ghco dot co.uk
2012-06-14  8:16 ` paul.scruby at ghco dot co.uk
2012-06-14 11:46 ` paul.scruby at ghco dot co.uk
2012-09-06 13:03 ` paul.scruby at ghco dot co.uk

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-53604-4-XyHD4jZe41@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).