Hello

I recently updated my repository (changeset:   8926:97f06a79b6f5) and now I am 
unable to build GEM5. The funny thing is that I don't get any error. I tried 
the default configuration (according to SConstruct this is 
build/ALPHA/gem5.debug) and the ALPHA_MOESI_CMP_directory but the result is 
always the same: no compilation and no GEM5 binary. Below you can see the 
output I get and a listing of the build/ and build/ALPHA/ directories:

machine:~/gem5$ scons
scons: Reading SConscript files ...

You're missing the gem5 style hook, which automatically checks your code
against the gem5 style rules on hg commit and qrefresh commands.  This
script will now install the hook in your .hg/hgrc file.
Press enter to continue, or ctrl-c to abort:  
Adding style hook to /home/alex/gem5/.hg/hgrc 

Checking for leading underscore in global variables...no
Checking for C header file Python.h... yes
Checking for C library pthread... yes
Checking for C library dl... yes
Checking for C library util... yes
Checking for C library m... yes
Checking for C library python2.7... yes
Checking for accept(0,0,0) in C++ library None... yes
Checking for zlibVersion() in C++ library z... yes
Checking for clock_nanosleep(0,0,NULL,NULL) in C library None... no
Checking for clock_nanosleep(0,0,NULL,NULL) in C library rt... yes
Checking for C header file fenv.h... yes
Reading SConsopts
Building in /home/alex/gem5/build/ALPHA
Variables file /home/alex/gem5/build/variables/ALPHA not found,
  using defaults in /home/alex/gem5/build_opts/ALPHA
Generating LALR tables
WARNING: 1 shift/reduce conflict
machine:~/gem5$ ls build/
ALPHA  gzstream  libelf  scons_config.log  sconsign.dblite  variables  
variables.global
machine:~/gem5$ ls build/ALPHA/
arch  base  cpu  dev  kern  mem  python  SConscript  sim  unittest
machine:~/gem5$ 

Am I doing something wrong? Am I forgetting some scons option?

Alexandru Iordan
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to