We don't run with old versions very often, but I'm not aware of anything that would make them horribly broken. What sort of errors are you getting? Maybe they're easy to fix. I imagine we'd at least have run into them over time and had to fix them in the current version of the code, so we might remember them.
Gabe On 01/31/11 19:59, Joel Hestness wrote: > Hi guys, > This is a long shot, but I'm having a terrible time trying to get an > old revision of the M5 to run. I have been using an old copy of the > /hg/m5 repo, changeset 5589 (October 2008), because I have patches > that don't work with newer revisions of the repo, and they would take > a bunch of debugging to update. Our cluster machines at UT were > updated last week (both hardware and distros), and I'm no longer able > to build or run on them. Does anyone happen to know which versions of > g++, Python, scons and swig were being used at the time? I've tried a > bunch of configurations to no avail. Also, was everything switched > over to build and run on 64-bit OSs by then? > Thanks! > Joel > > -- > Joel Hestness > PhD Student, Computer Architecture > Dept. of Computer Science, University of Texas - Austin > http://www.cs.utexas.edu/~hestness > <http://www.cs.utexas.edu/%7Ehestness> > > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
