From: Dave Brolley <brolley@redhat.com>
To: sid@sources.redhat.com
Subject: [patch] Running sidcomp.cgen-cpu.* tests using run-sid-tests-raw
Date: Tue, 28 Oct 2003 18:32:00 -0000 [thread overview]
Message-ID: <3F9EB626.7010409@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
I've committed the attached patch which allows run-sid-tests-raw to
work. find_rawsid is used by other tools to find sid and they typically
have the ,atching setting of tool_root_dir (i.e. the root of the build
tree). However, when running sidcomp.cgen-cpu.* tests tool_root_dir is
set to $build/sid, so sid_find_sid is the correct proc to use.
Dave
[-- Attachment #2: check-sid.ChangeLog --]
[-- Type: text/plain, Size: 107 bytes --]
2003-10-28 Dave Brolley <brolley@redhat.com>
* lib/cpudefs.exp (run-sid-tests-raw): Use sid_find_sid.
[-- Attachment #3: check-sid.patch.txt --]
[-- Type: text/plain, Size: 957 bytes --]
Index: sid/component/testsuite/lib/cpudefs.exp
===================================================================
RCS file: /cvs/src/src/sid/component/testsuite/lib/cpudefs.exp,v
retrieving revision 1.6
retrieving revision 1.7
diff -c -p -r1.6 -r1.7
*** sid/component/testsuite/lib/cpudefs.exp 29 Nov 2002 05:33:14 -0000 1.6
--- sid/component/testsuite/lib/cpudefs.exp 28 Oct 2003 18:24:59 -0000 1.7
*************** proc run-sid-tests-raw { toolchain-prefi
*** 44,50 ****
set as [sid_find_gas ${toolchain-prefix}]
set ld [sid_find_ld ${toolchain-prefix}]
! set sid [find_rawsid]
set runner sid-run-conf
foreach src [lsort [glob -nocomplain ${testcase-srcdir}/$pattern]] {
--- 44,50 ----
set as [sid_find_gas ${toolchain-prefix}]
set ld [sid_find_ld ${toolchain-prefix}]
! set sid [sid_find_sid]
set runner sid-run-conf
foreach src [lsort [glob -nocomplain ${testcase-srcdir}/$pattern]] {
reply other threads:[~2003-10-28 18:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F9EB626.7010409@redhat.com \
--to=brolley@redhat.com \
--cc=sid@sources.redhat.com \
/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).