It had happened to me. The eio tests may be failing if you dont have the 
encumbered files and havent compiled your m5 with the --extras option. But 
someone from M5 team may give a more definite answer.
  ----- Original Message ----- 
  From: HyoukJoong Lee 
  To: [email protected] 
  Sent: Thursday, July 30, 2009 6:33 PM
  Subject: [m5-users] M5 build error & regression test failures


  Hello.

  I'm a new user of M5, and now trying to build the M5 simulator.
  The M5 source codes are the latest source codes from the repository without 
any change.
  I'm using the VMware Player with Ubuntu on it, and the installed tools are 
the latest versions as below.

  $ uname -a
  Linux ubuntu 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 
GNU/Linux

  g++ : 4.3.3
  Python : 2.5.4
  SCons : 1.2.0
  SWIG : 1.3.36
  zlib : 1.2.3.3
  m4 : 1.4.13

  To build the M5 simulator, I used the command below.
  $ scons build/SPARC_SE/m5.debug

  The build process stops at o3_cpu_exec.cc file, and finally gives error after 
a while(about 10 minutes of stall).
  Below is the error message.
  ------------------------------------------------------------------
  g++ -o build/SPARC_SE/arch/sparc/o3_cpu_exec.do -c -Wno-deprecated -pipe 
-fno-strict-aliasing -Wall -Wno-sign-compare -Wundef -ggdb3 -Werror 
-DTHE_ISA=SPARC_ISA -DDEBUG -DTRACING_ON=1 -Ibuild/gzstream -Ibuild/libelf 
-Iext -I/usr/include/python2.5 -Ibuild/SPARC_SE 
build/SPARC_SE/arch/sparc/o3_cpu_exec.cc
  {standard input}: Assembler messages:
  {standard input}:268183: Warning: end of file not at end of a line; newline 
inserted
  {standard input}:268573: Error: expected comma after name 
`_ZNK12SparcISAInst9Bpr' in .size directive
  g++: Internal error: Killed (program cc1plus)
  Please submit a full bug report.
  See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions.
  scons: *** [build/SPARC_SE/arch/sparc/o3_cpu_exec.do] Error 1
  scons: building terminated because of errors.
  ------------------------------------------------------------------


  When I tried to build ALPHA_SE instead of SPARC_SE, 
  I could successfully build the simulator, but now some regression tests fail.

  ------------------------------------------------------------------
  $ scons build/ALPHA_SE/tests/debug/quick
  :
  :
  scons: Building targets ...
  ***** build/ALPHA_SE/tests/debug/quick/00.hello/alpha/linux/inorder-timing 
passed.
  ***** build/ALPHA_SE/tests/debug/quick/00.hello/alpha/linux/o3-timing passed.
  ***** build/ALPHA_SE/tests/debug/quick/00.hello/alpha/linux/simple-atomic 
passed.
  ***** build/ALPHA_SE/tests/debug/quick/00.hello/alpha/linux/simple-timing 
passed.
  ***** build/ALPHA_SE/tests/debug/quick/00.hello/alpha/tru64/o3-timing passed.
  ***** build/ALPHA_SE/tests/debug/quick/00.hello/alpha/tru64/simple-atomic 
passed.
  ***** build/ALPHA_SE/tests/debug/quick/00.hello/alpha/tru64/simple-timing 
passed.
  ***** build/ALPHA_SE/tests/debug/quick/01.hello-2T-smt/alpha/linux/o3-timing 
passed.
  ***** build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-atomic 
FAILED!
  ***** build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-timing 
FAILED!
  ***** build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-atomic-mp 
FAILED!
  ***** build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp 
FAILED!
  Running test in 
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest.
  build/ALPHA_SE/m5.debug -d 
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest -re 
tests/run.py build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest
  Redirecting stdout to 
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simout
  Redirecting stderr to 
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simerr
  <stopped here.......>
  ------------------------------------------------------------------

  As can be seen from above,
  the regression tests after (01.hello-2T-smt/alpha/linux/o3-timing) fail and 
50.memtest just stalls.

  I think this problem comes from the version mismatch of the tools,
  or using the vmware may not be a good idea.
  How could I handle this problem and successfully build the simulator?
  Can anybody tell me the version numbers of those tools,
  so that I could retry with those versions?

  Thanks.

  HyoukJoong.




------------------------------------------------------------------------------


  _______________________________________________
  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

Reply via email to