This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libstdc++ link failures on ppc64

From: "H. J. Lu" <hjl at lucon dot org>
To: Diego Novillo <dnovillo at redhat dot com>
Cc: Jon Grimm <jgrimm2 at us dot ibm dot com>, gcc at gcc dot gnu dot org,libstdc++ at gcc dot gnu dot org, Daniel Jacobowitz <drow at false dot org>,julian at codesourcery dot com
Date: Thu, 14 Apr 2005 09:52:48 -0700
Subject: Re: libstdc++ link failures on ppc64
References: <20050414133352.GA14133@topo.toronto.redhat.com> <425E99B9.4030609@us.ibm.com> <20050414164608.GA16489@topo.toronto.redhat.com>

On Thu, Apr 14, 2005 at 12:46:08PM -0400, Diego Novillo wrote:
> On Thu, Apr 14, 2005 at 11:26:33AM -0500, Jon Grimm wrote:
> > Diego Novillo wrote:
> > 
> > 
> > >
> > >I see no changes in libstdc++ since the previous run and nothing
> > >in the C++ FE, so I'm not sure whether it may be something broken
> > >in my box.
> > >
> > >Anybody else seeing this failure?
> > >
> > 
> > Yep. I see this here on the PPC64 nightly autotester.
> > 
> Undoing this patch fixes the build failure on ppc64 (though it
> doesn't affect the ld segfault on ia64 that I reported
> separately).  Thanks to drow and jbrown for pointing it out to
> me:
> 

You may need to upgrade your binutils to the one in CVS to get proper
COMDAT support.

BTW, I didn't get ld segfault on ia64. But all libjava tests failed.
I am looking into it now.


H.J.

References:
- libstdc++ link failures on ppc64
  - From: Diego Novillo
- Re: libstdc++ link failures on ppc64
  - From: Jon Grimm
- Re: libstdc++ link failures on ppc64
  - From: Diego Novillo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]