From: Ranjit Mathew <rmathew@gmail.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Test failure in libgcj on mainline
Date: Mon, 29 Nov 2004 10:48:00 -0000 [thread overview]
Message-ID: <39399b9d0411290112102f1120@mail.gmail.com> (raw)
In-Reply-To: <200411271841.iARIfN1V000195@hiauly1.hia.nrc.ca>
On Sat, 27 Nov 2004 13:41:23 -0500 (EST), John David Anglin
<dave@hiauly1.hia.nrc.ca> wrote:
> > Thanks John. However, I now see:
> >
> > Running /extra/src/gcc/gcc-20041127/libjava/testsuite/libjava.cni/cni.exp
> > ...
> > ERROR: (DejaGnu) proc "set_ld_library_path_env_vars" does not exist.
>
> I'm puzzled by this one. I didn't see it in my last build on i686-linux
> or hppa-linux:
>
> <http://gcc.gnu.org/ml/gcc-testresults/2004-11/msg01204.html>
> <http://gcc.gnu.org/ml/gcc-testresults/2004-11/msg01205.html>.
>
> The proc "set_ld_library_path_env_vars" is in
> gcc/gcc/testsuite/lib/target-libpath.exp. This file is loaded by
> libjava.exp. This is done using the same proc as other libraries
> use to load files in the gcc testsuite directory. This depends
> on the setting of srcdir in the libjava testsuite Makefile.
Today (2004-11-29, IST) I tried this on another machine
(i686-pc-linux-gnu) and did not see this problem. So I
guess it was a temporary disturbance in the force. :-/
Thanks,
Ranjit.
--
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/
next prev parent reply other threads:[~2004-11-29 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 13:44 John David Anglin
2004-11-27 18:41 ` Ranjit Mathew
2004-11-27 21:50 ` John David Anglin
2004-11-29 10:48 ` Ranjit Mathew [this message]
2004-11-30 13:55 ` Ranjit Mathew
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 12:46 Andrew Haley
2004-11-26 12:23 ` Ranjit Mathew
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=39399b9d0411290112102f1120@mail.gmail.com \
--to=rmathew@gmail.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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).