From: Steve Ellcey <sellcey@mips.com>
To: Richard Sandiford <rsandifo@linux.vnet.ibm.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, testsuite] Fix profile test failures
Date: Fri, 14 Feb 2014 17:24:00 -0000 [thread overview]
Message-ID: <1392398663.17835.120.camel@ubuntu-sellcey> (raw)
In-Reply-To: <87ppmqrlra.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com>
On Fri, 2014-02-14 at 11:12 +0000, Richard Sandiford wrote:
> Using target in itself should be OK. The hostname for rsh/ssh should be
> [board_info $board hostname] rather than $board itself. So in this case
> [board_info "multi-sim/-EL" hostname] should be multi-sim. The usual way
> to set that up is to put:
>
> set_board_info hostname multi-sim
>
> in multi-sim.exp.
>
> Thanks,
> Richard
Richard and Joseph, thanks for the pointers. I tried Richards change
and it partially fixed the problem. My board started doing an rsh/ssh
to 'multi-sim' instead of 'multi-sim/-EL' but that command times out
because multi-sim is not a machine that I can rsh/ssh to, it is just the
name of my dejagnu baseboard. Looking around some more I found sim.exp
in dejagnu (which I include in my board) and I see it has overrides for
load, upload, and download but no override for exec. I added this to
config/sim.exp:
proc sim_exec { dest srcfile args } {
return [remote_exec host $srcfile $args]
}
to match the sim_upload and sim_download definitions and things seem to
work now. In fact, now that I have this change to sim.exp I no longer
need to set hostname in multi-sim.exp.
I will submit the config/sim.exp patch to the dejagnu mailing list later
today.
Steve Ellcey
sellcey@mips.com
prev parent reply other threads:[~2014-02-14 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 22:10 Steve Ellcey
2014-02-13 23:10 ` Joseph S. Myers
2014-02-13 23:49 ` Steve Ellcey
2014-02-14 0:26 ` Joseph S. Myers
2014-02-14 11:12 ` Richard Sandiford
2014-02-14 17:24 ` Steve Ellcey [this message]
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=1392398663.17835.120.camel@ubuntu-sellcey \
--to=sellcey@mips.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=rsandifo@linux.vnet.ibm.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).