public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: joel@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Subject: c++/3930: mips-elf c++ testsuite can't find libstdc++ library
Date: Fri, 03 Aug 2001 12:46:00 -0000	[thread overview]
Message-ID: <20010803193632.3683.qmail@sourceware.cygnus.com> (raw)

>Number:         3930
>Category:       c++
>Synopsis:       mips-elf c++ testsuite can't find libstdc++ library
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 03 12:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     joel@gcc.gnu.org
>Release:        gcc-30-cvs 20010802
>Organization:
>Environment:
GNU/Linux RedHat 6.2 targetting mips-elf
>Description:
About 1800 test suite failures are of this form:

/usr3/ftp_archive/gnu/gcc/ss/b3/b-mips-elf/gcc/testsuite/../ld: cannot find -lst
dc++^M
collect2: ld returned 1 exit status^M
compiler exited with status 1
output is:
/usr3/ftp_archive/gnu/gcc/ss/b3/b-mips-elf/gcc/testsuite/../ld:  cannot find -lstdc++^M
collect2: ld returned 1 exit status^M

FAIL: g++.abi/primary2.C (test for excess errors)
/usr3/ftp_archive/gnu/gcc/ss/b3/b-mips-elf/gcc/testsuite/../ld:  cannot find -lstdc++
collect2: ld returned 1 exit status
>How-To-Repeat:
configure for mips-elf and run the tests.  I can provide support with binutils and simulator to someone investigating this.
>Fix:
unknown probably just a script/Makefile problem.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-08-03 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03 12:46 joel [this message]
2001-08-03 16:16 Hans-Peter Nilsson

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=20010803193632.3683.qmail@sourceware.cygnus.com \
    --to=joel@gcc.gnu.org \
    --cc=gcc-gnats@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).