public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14207] [3.4/3.5? Regression] Bootstrap fails linking libstdc++.so  for  -mabi-o32 ABI
Date: Thu, 19 Feb 2004 07:25:00 -0000	[thread overview]
Message-ID: <20040219072550.21287.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040219054655.14207.billingd@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-02-19 07:25 -------
This really sounds like a target specific problem.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |build
            Summary|Bootstrap fails linking     |[3.4/3.5? Regression]
                   |libstdc++.so  for  -mabi-o32|Bootstrap fails linking
                   |ABI                         |libstdc++.so  for  -mabi-o32
                   |                            |ABI
   Target Milestone|---                         |3.4.0


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


  reply	other threads:[~2004-02-19  7:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19  5:47 [Bug bootstrap/14207] New: " billingd at gcc dot gnu dot org
2004-02-19  7:25 ` pinskia at gcc dot gnu dot org [this message]
2004-02-20  3:30 ` [Bug bootstrap/14207] [3.4 Regression] " billingd at gcc dot gnu dot org
2004-02-20  5:14 ` billingd at gcc dot gnu dot org
2004-02-20  8:22 ` pcarlini at suse dot de
2004-02-20 19:54 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-02-25  3:19 ` cvs-commit at gcc dot gnu dot org
2004-02-25  3:28 ` billingd at gcc dot gnu dot org
2004-02-25  5:52 ` echristo at redhat dot com
2004-02-25  6:16 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-03-01  2:06 ` [Bug target/14207] " mmitchel at gcc dot gnu dot org
2004-03-01  2:15 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-03-08 23:11 ` mmitchel at gcc dot gnu dot org
2004-03-08 23:18 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-03-09 23:16 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-03-18 17:39 ` cvs-commit at gcc dot gnu dot org
2004-03-21 17:57 ` mmitchel at gcc dot gnu dot org
2004-03-21 18:02 ` pcarlini at suse dot de
2004-03-22  0:19 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-03-22  6:49 ` [Bug target/14207] [3.5 " mmitchel at gcc dot gnu dot org
2004-08-20 10:33 ` rsandifo 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=20040219072550.21287.qmail@sources.redhat.com \
    --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).