Re: [Gems-users] Ruby Compile Problem


Date: Tue, 14 Jul 2009 09:30:27 -0500
From: Polina Dudnik <pdudnik@xxxxxxxxx>
Subject: Re: [Gems-users] Ruby Compile Problem
Hi Chen,

So, one thing I notice is that you are compiling with gcc 4.3. People have reported some issues with it. Can you please try to include "string.h" in CacheMemory.h and see if it helps? Because I think what might be happening is that even though string.h is included somewhere the more recent version of gcc does not find it when compiling CacheMemory.h and so strcmp looks undeclared.

Please let us know whether or not it works.

Thanks.

Polina

On Mon, Jul 13, 2009 at 10:10 PM, Chen Cao <caochen.bupt@xxxxxxxxx> wrote:
Hi, I am new to GEMS, and I am now trying to set up Simics 3.0.31+GEMS 2.1 following the instruction from "Setup for Simics 3.0.X"(http://www.cs.wisc.edu/gems/doc/gems-wiki/moin.cgi/Setup_for_Simics_3.0.X) and a related document "GEMS-Ubuntu.pdf".
 
But when I complile Ruby, I encounterred some problem that I cannot fix.
Here is some information about the system:
 
[root@hadoop11 ruby]# uname -a
Linux hadoop11.hpclab 2.6.27.5-117.fc10.i686 #1 SMP Tue Nov 18 12:19:59 EST 2008 i686 i686 i386 GNU/Linux
[root@hadoop11 ruby]# gcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux
Thread model: posix
gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC)
 
and the problem I met was:
 
 [root@hadoop11 ruby]# make PROTOCOL=MOSI_SMP_bcast DESTINATION=MOSI_SMP_bcast
Ruby: Building protocol: MOSI_SMP_bcast
Ruby: Making slicc
cd ../slicc; make
make[1]: Entering directory `/home/hpclab/gems/slicc'
SLICC: Running flex and bison
make generated/generated
make[2]: Entering directory `/home/hpclab/gems/slicc'
make[2]: `generated/generated' is up to date.
make[2]: Leaving directory `/home/hpclab/gems/slicc'
SLICC: Building slicc executable
make x86-linux/bin/slicc.exec
make[2]: Entering directory `/home/hpclab/gems/slicc'
make[2]: `x86-linux/bin/slicc.exec' is up to date.
make[2]: Leaving directory `/home/hpclab/gems/slicc'
make[1]: Leaving directory `/home/hpclab/gems/slicc'
Ruby: Running slicc
make generated/MOSI_SMP_bcast/generated
make[1]: Entering directory `/home/hpclab/gems/ruby'
make[1]: `generated/MOSI_SMP_bcast/generated' is up to date.
make[1]: Leaving directory `/home/hpclab/gems/ruby'
Ruby: Generating ruby objects
make x86-linux/generated/MOSI_SMP_bcast/bin/tester.exec
make[1]: Entering directory `/home/hpclab/gems/ruby'
make[1]: Circular x86-linux/generated/MOSI_SMP_bcast/obj/init.o <- default_param.h dependency dropped.
/usr/bin/g++ -o x86-linux/generated/MOSI_SMP_bcast/obj/Chip.o -c generated/MOSI_SMP_bcast/Chip.C -DADD_ARCH_TO_API -DSIMICS30  -DIS_RUBY -DTARGET_X86 -DTARGET_VA_BITS=64 -DTARGET_PA_BITS=64     -Wall -W -Wwrite-strings -Woverloaded-virtual -Wno-unused  -march=i686 -g -ggdb -g3 -O2 -finline-functions -DNO_VECTOR_BOUNDS_CHECKS -DMULTIFACET_NO_OPT_WARN  -DRUBY_DEBUG=false  -Inetwork/simple -Inetwork/garnet-flexible-pipeline -I. -Inetwork/garnet-fixed-pipeline -Inetwork/orion -I../common -I../common/gzstream -Ibuffers -Icommon -Islicc_interface -Iprofiler -Iconfig -Ieventqueue -Isystem -Iinterfaces -Isimics -Itester -Irecorder -Ilog_tm -Irock -Igenerated/MOSI_SMP_bcast -I../common/ioutil -Inetwork -I/home/hpclab/gems/simics-3.0.31/src/include -I/home/hpclab/gems/simics-3.0.31/src/include/simics -I/home/hpclab/gems/simics-3.0.31/src/include/simics/core -I/home/hpclab/gems/simics-3.0.31/src/include/simics/arch -I/home/hpclab/gems/simics-3.0.31/src/include/simics/util 
In file included from /usr/lib/gcc/i386-redhat-linux/4.3.2/../../../../include/c++/4.3.2/ext/hash_map:64,
                 from ../common/std-includes.h:74,
                 from common/Global.h:108,
                 from generated/MOSI_SMP_bcast/Chip.h:8,
                 from generated/MOSI_SMP_bcast/Chip.C:3:
/usr/lib/gcc/i386-redhat-linux/4.3.2/../../../../include/c++/4.3.2/backward/backward_warning.h:33:2: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated.
In file included from generated/MOSI_SMP_bcast/Types.h:53,
                 from generated/MOSI_SMP_bcast/Chip.h:9,
                 from generated/MOSI_SMP_bcast/Chip.C:3:
system/CacheMemory.h: In constructor ‘CacheMemory<ENTRY>::CacheMemory(AbstractChip*, int, int, MachineType, const std::string&)’:
system/CacheMemory.h:208: error: there are no arguments to ‘strcmp’ that depend on a template parameter, so a declaration of ‘strcmp’ must be available
system/CacheMemory.h:208: error: (if you use ‘-fpermissive’, G++ will accept your code, but allowing the use of an undeclared name is deprecated)
system/CacheMemory.h:210: error: there are no arguments to ‘strcmp’ that depend on a template parameter, so a declaration of ‘strcmp’ must be available
system/CacheMemory.h: In constructor ‘CacheMemory<ENTRY>::CacheMemory(AbstractChip*, int, int, MachineType, const std::string&) [with ENTRY = L1Cache_Entry]’:
generated/MOSI_SMP_bcast/Chip.C:65:   instantiated from here
system/CacheMemory.h:208: error: ‘strcmp’ was not declared in this scope
make[1]: *** [x86-linux/generated/MOSI_SMP_bcast/obj/Chip.o] Error 1
make[1]: Leaving directory `/home/hpclab/gems/ruby'
make: *** [all] Error 2
 
I tried searching answers in the mailing list, but till now I havn't found a same issue, so I have to ask for all your help ^_^
 
Thank you all in advance
Best regards

_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.



[← Prev in Thread] Current Thread [Next in Thread→]