can't compile MV5 version 0.9

28 views
Skip to first unread message

Bin

unread,
Jan 7, 2012, 12:53:08 PM1/7/12
to mv5...@googlegroups.com


Hello,

I downloaded the latest version of MV5(0.9), but could not compile it successfully. 
Following is the log for a rebuild, which makes it concise. 

I know deleting the "-Werror" might help, but not sure whether it's the standard way to fix it.
Does anyone in the group have the same errors?

./scons/scons.py build/ALPHA_SE/m5.fast CPU_MODELS=O3CPU,TimingSimpleCPU,AtomicSimpleCPU,MTSimpleCPU,MTAtomicCPU,SIMDTimingCPU,ControlCPU,SlaveCPU
scons: Reading SConscript files ...
Checking for C header file Python.h... (cached) yes
Checking for C library python2.4... (cached) yes
Checking for accept(0,0,0) in C++ library None... (cached) yes
Checking for zlibVersion() in C++ library z... (cached) yes
Checking for C header file fenv.h... (cached) yes
Building in /home/bwang/projects/hgfractal/build/ALPHA_SE
Using saved options file /home/bwang/projects/hgfractal/build/options/ALPHA_SE
Compiling in ALPHA_SE with MySQL support.
scons: done reading SConscript files.
scons: Building targets ...
g++ -o build/ALPHA_SE/smp/simd/simt.fo -c -pipe -fno-strict-aliasing -Wall -Wno-sign-compare -Werror -Wundef -rdynamic -O3 -DTHE_ISA=ALPHA_ISA -DNDEBUG -DTRACING_ON=0 -Iext/dnet -I/usr/include/python2.4 -Ibuild/libelf -I/usr/include/mysql -Ibuild/ALPHA_SE build/ALPHA_SE/smp/simd/simt.cc
cc1plus: warnings being treated as errors
build/ALPHA_SE/smp/simd/simt.cc: In member function ‘void SIMT::adaptWidthDepthConstraint(int)’:
build/ALPHA_SE/smp/simd/simt.cc:1398: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 2 has type ‘Tick’
build/ALPHA_SE/smp/simd/simt.cc:1404: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 2 has type ‘Tick’
build/ALPHA_SE/sim/host.hh: At global scope:
build/ALPHA_SE/sim/host.hh:61: warning: ‘MaxTick’ defined but not used
build/ALPHA_SE/arch/alpha/isa_traits.hh:164: warning: ‘AlphaISA::SyscallPseudoReturnReg’ defined but not used
scons: *** [build/ALPHA_SE/smp/simd/simt.fo] Error 1
scons: building terminated because of errors.
make: *** [compileFAST] Error 2

Bin

unread,
Jan 7, 2012, 4:33:22 PM1/7/12
to mv5...@googlegroups.com

I think I have found the answer to my question in a very old thread. 

"For 32 bit machines with "printf("%lu", (Tick) tick), just convert it to "printf("%lu", (long unsigned int) tick)". 64-bit machines should be fine."

But i'm still wondering why we need to print out the ticks as long unsigned int. is there any other post processing?

Thanks.

Jiayuan Meng

unread,
Jan 7, 2012, 8:48:27 PM1/7/12
to mv5...@googlegroups.com
This is mainly a compatibility issue. Postprocessing is not necessary.

Jiayuan
Reply all
Reply to author
Forward
0 new messages