public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/18220] Test case libjava.lang/Process_3 does not end if "sed" not available
Date: Fri, 29 Oct 2004 18:10:00 -0000	[thread overview]
Message-ID: <20041029181019.31172.qmail@sourceware.org> (raw)
In-Reply-To: <20041029164522.18220.green@redhat.com>


------- Additional Comments From green at redhat dot com  2004-10-29 18:10 -------
It seems that all the Process_* test cases depend on having a small number of
simple executables on the target (false, sed, echo).  

It would nice if the testsuite could provide similar programs instead of
assuming they exist on the target (none of these existed on my minimal linux
target).  Rather than perform complicated dejagnu hackery, it might be easier to
attach the required programs as resources to the test programs themselves, and
then have the test case write them on the target filesystem before execution. 
Any strong objections to this idea?



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18220


  parent reply	other threads:[~2004-10-29 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 16:45 [Bug java/18220] New: " green at redhat dot com
2004-10-29 17:09 ` [Bug libgcj/18220] " pinskia at gcc dot gnu dot org
2004-10-29 18:10 ` green at redhat dot com [this message]
2004-10-29 18:13 ` pinskia at gcc dot gnu dot org
2004-10-29 18:24 ` green at redhat dot com
2005-05-17 20:40 ` daney at gcc dot gnu dot org
2005-05-18  0:52 ` cvs-commit at gcc dot gnu dot org
2005-05-18  1:00 ` cvs-commit at gcc dot gnu dot org
2005-05-18  1:05 ` daney at gcc dot gnu dot org
2005-06-05  7:52 ` 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=20041029181019.31172.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).