If you look at the build log carefully, ruby builds first in gems/ruby
folder (running slicc, creating .o files), and then move to gems/
simics directory and runs "make ruby." The latter part is how simics
modules are supposed to be compiled - look at gems/simics/modules
directory.
For that part of the build, you need to customize gems/simics/
compiler.mk file to point to the desired compiler. By default, it
points to the system compiler.
Byn
On Mar 18, 2010, at 11:31 PM, Edward Lee wrote:
Hi,
I compiled Ruby with gcc 4.x before but I started having some
problems. So, I am trying to install Ruby with gcc 3.x now. Even
though I removed all the binaries I know, and also did make clean I am
still getting an error at the end of the compilation:
Using the Simics 3.0 API for ruby module
CCLD ruby.so
make[2]: /usr/bin/g++: Command not found
CC is not set to /usr/bin/g++ any more. So, compilation uses the new
compiler up to that point but asking for the previous one at the end.
I tried to find a stronger clean in the makefile but couldn't find it.
Any ideas on this?
Thanks,
Ed
_______________________________________________
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.
|