public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: davem@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: java/7123: TLtest in java testsuite fails, regression on 3.1 branch from 3.1 release
Date: Tue, 25 Jun 2002 12:26:00 -0000 [thread overview]
Message-ID: <20020625190954.31142.qmail@sources.redhat.com> (raw)
>Number: 7123
>Category: java
>Synopsis: TLtest in java testsuite fails, regression on 3.1 branch from 3.1 release
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jun 25 12:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: davem@redhat.com
>Release: gcc-3.1 branch CVS
>Organization:
>Environment:
sparc-linux, sparc64-linux
>Description:
TLtest fails in the libjava testsuite.
The libjava.log file shows it trying to
build "Data$1.class" then gcj complains
that "/path/to/build/gcc/.class: no such
file or directory".
The "$1" is being expanded by the shell it
appears. So maybe the fix is simply to avoid
using the '$' character in testsuite file names.
>How-To-Repeat:
Bootstrap 3.1 branch, run libjava testsuite.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-06-25 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 12:26 davem [this message]
2002-06-25 12:34 Tom Tromey
2003-05-12 19:46 Dara Hazeghi
2003-05-13 6:36 steven
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=20020625190954.31142.qmail@sources.redhat.com \
--to=davem@redhat.com \
--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).