dejagnu
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nomenclature


From: Daniel Jacobowitz
Subject: Re: nomenclature
Date: Sat, 13 Aug 2005 16:34:10 -0400
User-agent: Mutt/1.5.8i

On Sat, Aug 13, 2005 at 09:30:03PM +0200, address@hidden wrote:
> Hello,
> 
> I'm using two machines. A is i386-linux, and B is arm-linux. I'm
> developing an application for B using A. That is:
> 
> For my compiler, arm-linux-gcc:
> 
> build:  i386-linux
> host:   i386-linux
> target: arm-linux
> 
> For my app's configure:
> 
> build:  i386-linux
> host:   arm-linux
> target: N/A
> 
> How are host and target defined for dejagnu?
> 
> I'm asking because I wrote a couple of testcases assuming that arm-linux
> is host. I used host_execute in my .exp files. The testcases run fine on
> A, but they don't get to B when I runtest --host_board=B. Should I use
> remote_exec in the .exp files and runtest --target_board=B?

Yes.  Your application is a native program, so it only uses build and
host.  DejaGNU is a cross-aware program, so it uses build, host, and
target: build is where dejagnu runs, host is where cross tools run by
dejagnu should run, target is your machine B.  In general, build !=
host for dejagnu isn't worth the trouble.

Also, host_execute doesn't do what you think it does.  You'd want
"remote_exec host" to run programs, and some other mechanism besides
host_execute to decide whether tests pass or fail.  I think
host_execute is just misnamed.

-- 
Daniel Jacobowitz
CodeSourcery, LLC




reply via email to

[Prev in Thread] Current Thread [Next in Thread]