Thank you for the quick response, but I still am having trouble finding this 
ARM directory. 

Here is what I have:

michael@ubuntu:~/Desktop/gem5-c739a3a829f5/build$ ls
gzstream  scons_config.log  variables
libelf    sconsign.dblite   variables.global

-Mike
________________________________________
From: gem5-users-boun...@gem5.org [gem5-users-boun...@gem5.org] on behalf of 
Anthony Gutierrez [atgut...@umich.edu]
Sent: Monday, April 02, 2012 5:58 PM
To: gem5 users mailing list
Subject: Re: [gem5-users] bbench/android

Oh, sorry. That is an artifact of the way the system used to be built. Now, the 
binaries for FS/SE are combined into a single binary. So to run you would do 
something like the follow:

./path_to_gem5_root/build/ARM/m5.fast configs/example/fs.py -b bbench 
--kernel=/path_to_gem5_system/binaries/vmlinux.smp.mouse.arm

I'll fix the wiki to reflect this.

On Mon, Apr 2, 2012 at 5:55 PM, Levine, Michael I 
<michael_lev...@student.uml.edu<mailto:michael_lev...@student.uml.edu>> wrote:

Hi,

I am an engineering graduate student and I am currently trying to run an 
android image using gem5. I am following these instructions:
http://www.m5sim.org/Bbench-gem5

However, I reach a snag when I get to this part:
Run /path_to_gem5_root/build/ARM_FS/m5.fast configs/example/fs.py -b bbench 
--kernel=vmlinux.smp.mouse.arm to run BBench on Android using ARM. Invoke from 
/path_to_gem5_root.

I don't seem to have an "ARM_FS" directory under my build directory. I have 
downloaded both the stable release of gem5 as well as the developer version.

Could you please point in the right direction of what I should do next?

Thanks!
Mike

_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto:gem5-users@gem5.org>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

--
Thanks,
Tony


<http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users>

_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to