We'll be releasing a version that fixes the gcc 4.1 incompatibilities.
Ali
On Mar 30, 2007, at 5:53 PM, [EMAIL PROTECTED] wrote:
M5 2.0 has a similar problem with gcc 4.1.+ as well. I moved back
to gcc 4.0.0
and everything worked!
-Mojtaba
Quoting Steve Lieberman <[EMAIL PROTECTED]>:
Ha
M5 2.0 has a similar problem with gcc 4.1.+ as well. I moved back to gcc 4.0.0
and everything worked!
-Mojtaba
Quoting Steve Lieberman <[EMAIL PROTECTED]>:
>
> Has anyone encountered build problems with gcc 4.1 such as the following?
>
>
> g++ -pipe -fno-strict-aliasing -Wall -Wno-sign-compare -
Has anyone encountered build problems with gcc 4.1 such as the following?
g++ -pipe -fno-strict-aliasing -Wall -Wno-sign-compare -Werror -Wundef -g
-O5 -m32 -fPIC -Iext/dnet -IALPHA -Im5 -c -o ALPHA/arch/alpha/decoder.os
ALPHA/arch/alpha/decoder.cc
cc1plus: warnings being treated as errors
m5/a