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 target/30572]  New: [4.3 Regression] libstdc++ links against /libgcc_s.1.dylib instead of $(prefix)/lib/libgcc_s.1.dylib
Date: Wed, 24 Jan 2007 06:31:00 -0000	[thread overview]
Message-ID: <bug-30572-6528@http.gcc.gnu.org/bugzilla/> (raw)

I don't know when this broke but this has been here between 
http://gcc.gnu.org/ml/gcc-testresults/2007-01/msg00121.html (rev 120402)
and
http://gcc.gnu.org/ml/gcc-testresults/2007-01/msg00134.html (rev 120429)

For some reason I think this was caused by the toplevel libgcc which was
introduced inbetween those revisions.  Also I thought I tested toplevel libgcc
on ppc-darwin with getting no failures.


-- 
           Summary: [4.3 Regression] libstdc++ links against
                    /libgcc_s.1.dylib instead of
                    $(prefix)/lib/libgcc_s.1.dylib
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
GCC target triplet: powerpc-darwin


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


             reply	other threads:[~2007-01-24  6:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24  6:31 pinskia at gcc dot gnu dot org [this message]
2007-01-24  6:32 ` [Bug target/30572] " pinskia at gcc dot gnu dot org
2007-01-24  6:35 ` pinskia at gcc dot gnu dot org
2007-01-24  6:40 ` echristo at apple dot com
2007-01-24 18:57 ` echristo at apple dot com
2007-04-18 17:44 ` echristo at apple dot com
2007-06-09 18:55 ` pinskia at gcc dot gnu dot org
2007-06-29 17:51 ` [Bug target/30572] [4.3 Regression] target libraries " mmitchel at gcc dot gnu dot org
2007-08-20  9:13 ` pinskia at gcc dot gnu dot org
2007-08-20 17:11 ` echristo at apple dot com
2007-10-28  4:31 ` pinskia at gcc dot gnu dot org
2007-10-31 22:00 ` pinskia at gcc dot gnu dot org
2007-11-01 17:09 ` echristo at apple dot com
2007-11-18 20:06 ` pinskia at gcc dot gnu dot org
2007-11-25  4:10 ` fang at csl dot cornell dot edu
2007-11-28  9:19 ` ek dot kato at gmail dot com
2007-11-29  9:08 ` ek dot kato at gmail dot com
2007-12-16 21:52 ` howarth at nitro dot med dot uc dot edu
2007-12-17  2:02 ` ek dot kato at gmail dot com
2007-12-17  2:55 ` howarth at nitro dot med dot uc dot edu
2007-12-17 23:26 ` echristo at apple dot com
2007-12-18  0:23 ` howarth at nitro dot med dot uc dot edu
2007-12-18  2:20 ` ek dot kato at gmail dot com
2007-12-18  8:35 ` bonzini at gnu dot org
2007-12-19  4:38 ` howarth at nitro dot med dot uc dot edu
2007-12-19 14:29 ` bonzini at gcc dot gnu dot org
2007-12-19 14:48 ` jakub at gcc dot gnu dot org
2008-02-29 14:07 ` howarth at nitro dot med dot uc dot edu

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-30572-6528@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).