The problem was at my end, after trying different versions of build-dependencies, swig was the problem. Swig versions 2.0.7 and 2.0.8 both break garnet; I am now using 2.0.4, which works. I would recommend to anyone else having this issue to use an older version of swig.
-- Marco On 28/09/12 23:19, Nilay Vaish wrote: > On Fri, 28 Sep 2012, Marco Elver wrote: > >> Hi all, >> >> I am having a problem with a setup that used to work. The important flag >> is --garnet-network, without which everything works just fine. >> >> Versions from before Sep 05 in the dev repo were working, unfortunately >> I don't have the exact commit when it stopped working; if nobody has an >> idea what is going wrong, I'll start bisecting. >> >> Does anyone have an idea where to start looking to fix it? (See attached >> *.log files for gem5 output) >> > > Likely that the problem is at your end. The following command line is > works when I execute it on my machine -- > > ./build/X86/gem5.debug ./configs/example/ruby_mem_test.py --functional > 10 -l 4000 -n 16 --num-l2caches 16 --num-dirs 16 --topology Mesh > --mesh-rows 4 --garnet-network=flexible > > > I would suggest that you remove the build directory and recompile gem5. > > -- > Nilay > -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
