public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>
To: rth@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/6212: g++ testsuite EH regressions for irix6 -mabi=64
Date: Tue, 16 Apr 2002 19:26:00 -0000	[thread overview]
Message-ID: <20020417022602.17275.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/6212; it has been noted by GNATS.

From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: <gcc-bugs@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc: <rth@gcc.gnu.org>
Subject: RE: c++/6212: g++ testsuite EH regressions for irix6 -mabi=64
Date: Wed, 17 Apr 2002 12:22:29 +1000

 It isn't a harness issue (fixed that).  I see a link warning:
 
 ld64: WARNING 127: Two shared objects with the same soname, =
 /usr/lib64/mips3/libm.so and /usr/lib64/libm.so, have been been linked. =
 This is probably due to a missing -L specification. Ignoring the latter.
 
 I will rebuild with --disable-shared (overnight).
 
 
 -----Original Message-----
 From: rth@gcc.gnu.org [mailto:rth@gcc.gnu.org]
 Sent: Wednesday, 17 April 2002 12:06=20
 To: Billinghurst, David (CRTS); gcc-bugs@gcc.gnu.org;
 gcc-prs@gcc.gnu.org; ghazi@caip.rutgers.edu; kenner@vlsi1.ultra.nyu.edu;
 rth@gcc.gnu.org
 Subject: Re: c++/6212: g++ testsuite EH regressions for irix6 -mabi=3D64
 
 
 Synopsis: g++ testsuite EH regressions for irix6 -mabi=3D64
 
 State-Changed-From-To: open->feedback
 State-Changed-By: rth
 State-Changed-When: Tue Apr 16 19:06:28 2002
 State-Changed-Why:
     Are you not seeing a testsuite harness problem?  E.g.
    =20
     884955:./array1.exe: rld: Fatal Error: Cannot Successfully map =
 soname 'libstdc++.so.5' under any of the filenames =
 ./libstdc++.so.5:/holodeck/work/law/rth/build/gcc/libstdc++.so.5:/usr/lib=
 64/libstdc++.so.5:/usr/lib64/internal/libstdc++.so.5:/lib64/libstdc++.so.=
 5:/opt/lib64/libstdc++.so.5:./libstdc++.so.5.5:/holodeck/work/law/rth/bui=
 ld/gcc/libstdc++.so.5.5:/usr/lib64/libstdc++.so.5.5:/usr/lib64/internal/l=
 ibstdc++.so.5.5:/lib64/libstdc++.so.5.5:/opt/lib64/libstdc++.so.5.5:=20
    =20
     Do you see the same failures if you configure with --disable-shared?
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D=
 gcc&pr=3D6212


             reply	other threads:[~2002-04-17  2:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 19:26 Billinghurst, David (CRTS) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-06 22:46 rth
2002-04-30 23:26 Richard Henderson
2002-04-30 21:56 Kaveh R. Ghazi
2002-04-30 21:36 Richard Henderson
2002-04-30 20:36 Billinghurst, David (CRTS)
2002-04-24 11:14 rth
2002-04-23  0:38 rth
2002-04-22 19:26 Billinghurst, David (CRTS)
2002-04-22  3:46 Richard Kenner
2002-04-21 21:06 Billinghurst, David (CRTS)
2002-04-21 20:46 Billinghurst, David (CRTS)
2002-04-17 17:56 Kaveh R. Ghazi
2002-04-17 17:16 Billinghurst, David (CRTS)
2002-04-16 19:06 rth
2002-04-16 18:07 rth
2002-04-06 22:56 David.Billinghurst

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=20020417022602.17275.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rth@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).