public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/28701] New: ABI test failures building libstdc++ on a glibc-2.4 based system
Date: Fri, 11 Aug 2006 22:46:00 -0000 [thread overview]
Message-ID: <bug-28701-11764@http.gcc.gnu.org/bugzilla/> (raw)
Building 4.1.x on powerpc-linux-gnu and sparc-linux-gnu lets the libstdc++ ABI
check fail (log attached); a libstlport4.6 built on a glibc-2.3.6 system cannot
resolve the references to the libstdc++6 built on the glibc-2.4 system.
--
Summary: ABI test failures building libstdc++ on a glibc-2.4
based system
Product: gcc
Version: 4.1.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: doko at ubuntu dot com
GCC target triplet: powerpc-linux-gnu sparc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28701
next reply other threads:[~2006-08-11 22:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 22:46 doko at ubuntu dot com [this message]
2006-08-11 22:47 ` [Bug target/28701] " doko at ubuntu dot com
2006-08-11 22:50 ` pinskia at gcc dot gnu dot org
2006-08-13 16:33 ` [Bug target/28701] [4.1/4.2 regression] " pinskia at gcc dot gnu dot org
2006-08-17 12:38 ` jakub at gcc dot gnu dot org
2006-08-23 10:20 ` doko at ubuntu dot com
2006-09-01 21:51 ` mmitchel at gcc dot gnu dot org
2006-09-04 11:28 ` jakub at gcc dot gnu dot org
2006-09-04 12:14 ` jakub at gcc dot gnu dot org
2006-10-04 17:36 ` debian-gcc at lists dot debian dot org
2006-10-04 22:03 ` jakub at gcc dot gnu dot org
2006-10-05 15:13 ` debian-gcc at lists dot debian dot org
2006-10-05 15:40 ` pinskia at gcc dot gnu dot org
2007-02-14 9:01 ` [Bug target/28701] [4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-03-12 18:31 ` mmitchel 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=bug-28701-11764@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).