On Sat, Aug 13, 2005 at 09:30:03PM +0200, [EMAIL PROTECTED] 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 _______________________________________________ DejaGnu mailing list DejaGnu@gnu.org http://lists.gnu.org/mailman/listinfo/dejagnu
