Re: [Gems-users] Using Multiple CC Protocols

[Daniel Sánchez Pedreño <sanatox@xxxxxxxxx>]

As Greg pointed out before, the problem is in the movemodule function of Ruby Makefile

> movemodule:
> ifeq ($(SIMICS_VERSION),2.2.X)
>         $(GEMS_ROOT)/scripts/prepare_simics_home.sh $(SIMICS_ROOT)/home/$(DESTINATION) $(HOST_TYPE)
>         $(MV) $(SIMICS_ROOT)/$(HOST_TYPE)/lib/ruby.so $(SIMICS_ROOT)/home/$(DESTINATION)/modules/ruby-v9.so
>         $(MV) $(SIMICS_ROOT)/$(HOST_TYPE)/lib/python/mod_ruby_commands.py $(SIMICS_ROOT)/home/$(DESTINATION)/modules/python
> else
> ifeq ($(SIMICS_VERSION),3.0)
>         $(GEMS_ROOT)/scripts/prepare_simics_home.sh $(SIMICS_EXEC_ROOT)/home/$(DESTINATION) $(HOST_TYPE)
>         $(MV) $(SIMICS_EXEC_ROOT)/$(HOST_TYPE)/lib/ruby.so $(SIMICS_EXEC_ROOT)/home/$(DESTINATION)/modules/ruby-v9.so
>         $(MV) $(SIMICS_EXEC_ROOT)/$(HOST_TYPE)/lib/python/mod_ruby_commands.py $(SIMICS_EXEC_ROOT)/home/$(DESTINATION)/modules/python
> else
>         @echo "Unrecognized value for SIMICS_VERSION: see common/Makefile.common"
>         exit 1
> endif
> endif

For some reason, the move command is not performed when the simics version is 3.0. So you just have to add the bolded lines in order to solve your problem. For me is working.

I think this patch should be included in future Makefile versions because this error could lead to missunderstandings. It has been driving me crazy until I found where the error was!!!

Regards