Part of the problem with using an old version is that you will be missing
bug fixes and also patches needed for compatibility with newer compiler
versions.  So you basically have to track down and fix problems like this on
your own, though you can look through the mailing list archives or the
change log to find the patches that fix these problems and try to apply them
to the old code.

BTW, since you're rolling back to an old version anyway, you might as well
clone the development repository rather than the stable one, so you have all
the latest changes in your log.

Steve

2011/9/12 THX <[email protected]>

>
> Steve, thanks for your information. I am not sure whether the m5 directory
> I copied includes the whole repository or not. So I tried clone gem5-stable
> via "hg clone http://repo.gem5.org/m5-stable"; then degrade to beta 6 via
> the command you gave. This step works. And when I build it via
> scons build/ALPHA_SE/m5.fast
>
> it began successfully until errors shown as:
>
> ...
> g++ -o build/ALPHA_SE/base/annotate.fo -c -Wno-deprecated -pipe
> -fno-strict-aliasing -Wall -Wno-sign-compare -Werror -Wundef -O3
> -DTHE_ISA=ALPHA_ISA -DNDEBUG -DTRACING_ON=0 -Iext/dnet
> -I/usr/include/python2.7 -Ibuild/libelf -Ibuild/ALPHA_SE
> build/ALPHA_SE/base/annotate.cc
> g++ -o build/ALPHA_SE/base/atomicio.fo -c -Wno-deprecated -pipe
> -fno-strict-aliasing -Wall -Wno-sign-compare -Werror -Wundef -O3
> -DTHE_ISA=ALPHA_ISA -DNDEBUG -DTRACING_ON=0 -Iext/dnet
> -I/usr/include/python2.7 -Ibuild/libelf -Ibuild/ALPHA_SE
> build/ALPHA_SE/base/atomicio.cc
> g++ -o build/ALPHA_SE/base/bigint.fo -c -Wno-de precated -pipe
> -fno-strict-aliasing -Wall -Wno-sign-compare -Werror -Wundef -O3
> -DTHE_ISA=ALPHA_ISA -DNDEBUG -DTRACING_ON=0 -Iext/dnet
> -I/usr/include/python2.7 -Ibuild/libelf -Ibuild/ALPHA_SE
> build/ALPHA_SE/base/bigint.cc
> In file included from build/ALPHA_SE/base/bigint.cc:31:0:
> build/ALPHA_SE/base/bigint.hh:39:5: error: ‘uint64_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:40:5: error: ‘uint64_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:43:23: error: ‘uint64_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:43:32: error: ISO C++ forbids declaration of
> ‘x’ with no type
> build/ALPHA_SE/base/bigint.hh:48:41: error: ‘uint64_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:48:50: error: ISO C++ forbids declaration of
> ‘x’ with no type
> build/ALPHA_SE/base/bigint.hh:55:14: error: expected type-specifier before
> ‘uint64_t’
> build/ALPHA_SE/base/bigint.hh: In constructor
> ‘m5_twin64_t::m5_twin64_t(int)’:
> build/ALPHA_ SE/base/bigint.hh:45:9: error: ‘a’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.hh:46:9: error: ‘b’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.hh: In member function ‘m5_twin64_t&
> m5_twin64_t::operator=(int)’:
> build/ALPHA_SE/base/bigint.hh:50:9: error: ‘a’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.hh:51:9: error: ‘b’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.hh: At global scope:
> build/ALPHA_SE/base/bigint.hh:63:5: error: ‘uint32_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:64:5: error: ‘uint32_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:67:23: error: ‘uint32_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:67:32: error: ISO C++ forbids declaration of
> ‘x’ with no type
> build/ALPHA_SE/base/bigint.hh:72:41: error: ‘uint32_t’ does not name a type
> build/ALPHA_SE/base/bigint.hh:72:50: error: ISO C++ forbids declaration of
> ‘x’ with no type
> build/ALPHA_SE/base/bigint.hh:79:14: error: expected type-specifier before
> ‘uint32_t’
> build/ALPHA_SE/base/bigint.hh: In constructor
> ‘m5_twin32_t::m5_twin32_t(int)’:
> build/ALPHA_SE/base/bigint.hh:69:9: error: ‘a’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.hh:70:9: error: ‘b’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.hh: In member function ‘m5_twin32_t&
> m5_twin32_t::operator=(int)’:
> build/ALPHA_SE/base/bigint.hh:74:9: error: ‘a’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.hh:75:9: error: ‘b’ was not declared in this
> scope
> build/ALPHA_SE/base/bigint.cc: In function ‘std::ostream&
> operator<<(std::ostream&, const Twin64_t&)’:
> build/ALPHA_SE/base/bigint.cc:39:13: error: ‘const struct Twin64_t’ has no
> member named ‘a’
> build/ALPHA_SE/base/bigint.cc:39:28: error: ‘const struct Twin64_t’ has no
> member named ‘b’
> build/ALPHA_SE/base/bigint.cc: In function ‘std::ostr eam&
> operator<<(std::ostream&, const Twin32_t&)’:
> build/ALPHA_SE/base/bigint.cc:45:13: error: ‘const struct Twin32_t’ has no
> member named ‘a’
> build/ALPHA_SE/base/bigint.cc:45:28: error: ‘const struct Twin32_t’ has no
> member named ‘b’
> scons: *** [build/ALPHA_SE/base/bigint.fo] Error 1
> scons: building terminated because of errors.
>
> Any clues on it?
>
> Regards,
> HX
>
> ------------------------------
> Date: Mon, 12 Sep 2011 08:39:53 -0700
> From: [email protected]
> To: [email protected]
> Subject: Re: [gem5-users] How can I get a the old beta6 version of m5?
>
>
>
> 2011/9/11 THX <[email protected]>
>
>
> Does anybody know how I can get a runnable m5 beta6 version?
>
> If you cloned the full mercurial repository, you should be able to do:
>   hg update -r m5_2.0_beta6
>
>
> And, is there any plan to modify the documents in gem5.org to support
> current gem5?
>
>
> It's of course our intention that the wiki be up to date.  If you're having
> trouble with the scripts on that page, please be specific about the errors
> you're getting and we can try and address them on the list.  Ideally we
> would then update the wiki as well, but if you're willing to help, it would
> be great if you would register for an account and fix them yourself.
>
> Steve
>
>
> _______________________________________________ gem5-users mailing list
> [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to