It's a scons issue with a missing dependency. A patch will be posted
shortly. 

Ali 

On 07.09.2012 07:52, Andreas Hansson wrote: 

> Hi
everyone,
> 
> After a bit of digging, it seems the Ruby regressions
that make use of the clocked memory controller are all breaking, and all
it takes to fix them is a clean build.
> 
> Somehow, setting the clock =
"400MHz" in the Python object doesn't end up having any effect, and the
clock ends up being 0. swig ninjas out there, any ideas?
> 
> Thanks,
>

> Andreas
> 
> -- IMPORTANT NOTICE: The contents of this email and any
attachments are confidential and may also be privileged. If you are not
the intended recipient, please notify the sender immediately and do not
disclose the contents to any other person, use it for any purpose, or
store or copy the information in any medium. Thank you.
>
_______________________________________________
> gem5-dev mailing
list
> [email protected]
> http://m5sim.org/mailman/listinfo/gem5-dev

 
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to