public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rankincj at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/26922] Compile/link failure with -frepo and g++ 4.1
Date: Sat, 01 Apr 2006 23:00:00 -0000	[thread overview]
Message-ID: <20060401230047.13945.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26922-2761@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]



------- Comment #6 from rankincj at yahoo dot com  2006-04-01 23:00 -------
Subject: Re:  Compile/link failure with -frepo and g++ 4.1

--- pinskia at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org> wrote:
> Well if you read the instructions on how to report a bug, a tar file is not
> really liked :).

And yet you allow tar files anyway.

Regardless, according to the RedHat bugzilla, this issue has been traced(?) to
a change in the
binutils linker. (Although I don't know if the linker is at fault, or whether
the collect2 helper
application is missing a change.)

Cheers,
Chris



___________________________________________________________ 
Yahoo! Photos – NEW, now offering a quality print service from just 8p a photo
http://uk.photos.yahoo.com


-- 


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


  parent reply	other threads:[~2006-04-01 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 15:34 [Bug c++/26922] New: " rankincj at yahoo dot com
2006-03-29 15:36 ` [Bug c++/26922] " rankincj at yahoo dot com
2006-03-29 21:10 ` rankincj at yahoo dot com
2006-03-29 23:22 ` pinskia at gcc dot gnu dot org
2006-03-29 23:44 ` rankincj at yahoo dot com
2006-03-31  0:32 ` pinskia at gcc dot gnu dot org
2006-04-01 23:00 ` rankincj at yahoo dot com [this message]
2006-04-02  6:17 ` pinskia 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=20060401230047.13945.qmail@sourceware.org \
    --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).