public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ajd at gentrack dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/13391] AIX: collect2 emits bad code with duplicated symbols
Date: Thu, 04 Mar 2004 06:15:00 -0000 [thread overview]
Message-ID: <20040304061515.17873.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031212191310.13391.greed@pobox.com>
------- Additional Comments From ajd at gentrack dot com 2004-03-04 06:15 -------
(In reply to comment #27)
> Subject: Re: AIX: collect2 emits bad code with duplicated symbols
> Something is broken with the build process. Only the single
> shared object should be present.
> David
I don't follow the Makefile.am / libtool jaz for libstdc++.
It may be related to --disable-symvers?
I had a build error without this option.
I will try again to see what this error was tomorrow.
From: http://gcc.gnu.org/install/specific.html#*-ibm-aix*
> Building libstdc++.a requires a fix for an AIX Assembler bug APAR IY26685
(AIX 4.3) or APAR IY25528 (AIX 5.1).
Does this apply to AIX 5.2 also?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13391
next prev parent reply other threads:[~2004-03-04 6:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 19:13 [Bug target/13391] New: AIX: crash on throw/catch between shared objects greed at pobox dot com
2003-12-12 19:18 ` [Bug target/13391] " greed at pobox dot com
2003-12-12 19:19 ` greed at pobox dot com
2003-12-12 19:19 ` greed at pobox dot com
2003-12-12 19:20 ` greed at pobox dot com
2003-12-12 19:20 ` greed at pobox dot com
2003-12-12 19:20 ` greed at pobox dot com
2003-12-24 2:46 ` ddurham_gcc_bz at davyandbeth dot com
2003-12-26 3:20 ` dje at gcc dot gnu dot org
2003-12-29 16:24 ` ddurham_gcc_bz at davyandbeth dot com
2003-12-29 20:51 ` greed at pobox dot com
2004-01-18 17:58 ` dhazeghi at yahoo dot com
2004-01-19 4:32 ` dje at watson dot ibm dot com
2004-01-19 17:36 ` [Bug target/13391] AIX: collect2 emits bad code with duplicated symbols dhazeghi at yahoo dot com
2004-01-20 21:13 ` greed at pobox dot com
2004-03-03 1:11 ` ajd at gentrack dot com
2004-03-03 22:48 ` dje at watson dot ibm dot com
2004-03-04 0:00 ` ajd at gentrack dot com
2004-03-04 1:56 ` ajd at gentrack dot com
2004-03-04 2:40 ` greed at pobox dot com
2004-03-04 2:47 ` dje at watson dot ibm dot com
2004-03-04 3:01 ` greed at pobox dot com
2004-03-04 4:01 ` ajd at gentrack dot com
2004-03-04 4:06 ` dje at watson dot ibm dot com
2004-03-04 4:16 ` ajd at gentrack dot com
2004-03-04 5:35 ` dje at watson dot ibm dot com
2004-03-04 5:56 ` ajd at gentrack dot com
2004-03-04 6:11 ` dje at watson dot ibm dot com
2004-03-04 6:15 ` ajd at gentrack dot com [this message]
2004-03-04 15:34 ` dje at watson dot ibm dot com
2004-03-04 17:17 ` greed at pobox dot com
2004-03-04 17:24 ` dje at watson dot ibm dot com
2004-03-04 17:28 ` dje at watson dot ibm dot com
2004-03-04 17:36 ` greed at pobox dot com
2004-03-04 18:46 ` dje at watson dot ibm dot com
2004-03-04 21:02 ` ajd at gentrack dot com
2004-03-05 15:44 ` greed at pobox dot com
2004-03-05 18:55 ` greed at pobox dot com
2004-03-05 19:51 ` dje at watson dot ibm dot com
2004-03-05 21:08 ` greed at pobox dot com
2004-03-06 20:56 ` dje at gcc dot gnu dot org
2004-03-06 23:31 ` pinskia at gcc dot gnu dot org
2004-03-07 22:35 ` dje at gcc dot gnu dot org
2004-11-24 18:42 ` 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=20040304061515.17873.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).