Hi Dan,
Thanks for your advice. It worked for gcc-4.0.3. Here's the deal. For every makefile, I had to change the LDFLAGS and MODULE_LDFLAGS variables to point to the non-native lib folder. Moreover, the SHELL variable in the common/Makefile.common was set to /bin/sh whereas I was using /bin/bash. At the end, I checked ruby.so, first using ldd and then objdump -T. All the proper files were linked and ruby.so had just one entry for ruby_session_set whereas previosuly it had two entries.
When I first start simics from the MOSI_SMP_bcast directory, and do a "load-module ruby" it gives me the error as:
/***************************************************************************\
> Physical Memory object cannot be found. If you are NOT compiling Ruby and <
> you see this message, something is wrong. <
> This message is part of the normal compilation process. <
\***************************************************************************/
Although, the gems-1.3.1 ruby.C file has that patch, still it is throwing this error for the first time. The second time it loads ruby.
Now if I try to run the command "ruby0.setparam g_NUM_PROCESSOR 1" in simics, it is giving me an error message as:
"attribute param in object ruby0: not found"
In fact, although it shows all the attributes of ruby0 when I press TAB, but it cannot find any of them and throws the above error message for all of them.
Thanks and regards,
Kushal.
_______________________________________________
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.