From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31232 invoked by alias); 29 Oct 2004 18:10:21 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 31173 invoked by uid 48); 29 Oct 2004 18:10:19 -0000 Date: Fri, 29 Oct 2004 18:10:00 -0000 Message-ID: <20041029181019.31172.qmail@sourceware.org> From: "green at redhat dot com" To: java-prs@gcc.gnu.org In-Reply-To: <20041029164522.18220.green@redhat.com> References: <20041029164522.18220.green@redhat.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/18220] Test case libjava.lang/Process_3 does not end if "sed" not available X-Bugzilla-Reason: CC X-SW-Source: 2004-q4/txt/msg00275.txt.bz2 List-Id: ------- 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