I just updated my repository and ran these two commands:
scons -j 8 EXTRAS=../encumbered build/ALPHA_SE/tests/debug/quick
scons -j 8 build/ALPHA_SE/tests/opt/quick

and got no build errors and no test failures.

This was on our regression machine, so the EIO traces are in a common
shared directory there, not in the repository.  So it's no surprise that
the EIO tests failed for you.  Unless you really want to use EIO traces, I
wouldn't worry about them.  The fact that you had to copy the headers is
odd though; I didn't need to do that.

The memtest failure is more bothersome.  Are you sure the test was rerun
after you updated to the non-stable repository?  If so, it might be worth
doing a clean build (you can do "scons -c", or just "rm -rf build").

Steve

On Wed, Dec 28, 2011 at 6:06 PM, Eliot Moss <m...@cs.umass.edu> wrote:

> Ok, I found in the FAQ about using EXTRAS to
> get EIO built in ... it almost worked to build,
> but I had to copy two .h/.hh files over to the
> build tree by hand.
>
> But I get the same 6 failures, 5 EIO and 1 memtest.
>
> For the EIO failures I ask: where is anagram?  Do I
> also need some set of benchmarks installed?
>
> Cheers -- Eliot
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to