Re: [Gems-users] Problems with -sign-module

[Dan Gibson <degibson@xxxxxxxx>]

We test locally with GCC 3.4.1, CentOS 4, Simics 3.0.11, Gems 1.4.
There have been many folks on this list that have successfully used 
Gems+Simics3 under a variety of compiler and OS flavors.
Perhaps the best option would be for you to start fresh with Gems 1.4. A 
re-install often fixes the most stubborn bugs of this type.
Regards,
Dan

Carles Hernández wrote:
> Dan,
> The function init_local() isn't reached. The problem seems to be in 
> $SIMICS_INSTALL/config/module.mk when it tries to sign the module that 
> has just been  compiled.  So, the problem is that the compiled module is 
> rejected when simics tries to sign it, and the make process removes the 
> module.
> Anyway could be helpfull for me to know some working configuration of 
> Simics 3.0 with gems, that is: OS, gcc version, simics subversion and 
> gems version.
> Thank you
>    
>
> Dan Gibson escribió:
>   
> > Ok, lets try a different approach.
> >
> > If Simics is crashing when loading Ruby for module signing, then we 
> > should verify that ruby/module/ruby.c is executing the correct code at 
> > load-time.
> > Have a look at ruby/module/ruby.c, at about lines 268-293. These lines 
> > in Gems 1.3.1 are intended to catch case where Simics loads Ruby for 
> > "signing". However, if for whatever reason  SIMICS_3_0 isn't 
> > #define'd, then problems could arise.
> > To debug your problem, try the following:
> >  * Add the following right after the #include's, (approx line 76). 
> > This will "permanently" convert your ruby/module/ruby.c to Simics 3.0.
> > #ifndef SIMICS_3_0
> > #define SIMICS_3_0
> > #endif
> >
> >  * If that doesn't work,  populate the init_local() function with 
> > printf() calls every few lines to try to determine where the error occurs.
> > Regards,
> > Dan
> >
> > Carles Hernández wrote:
> >     
> > >     Dan,
> > >     I have set the GEMS_ROOT variable to $(SRC_BASE). I've compiled ruby 
> > > and simics many times, but always appears the same error (Error 2) after 
> > > building ruby. I've succesfully installed Gems with simics 2.0.X, but I 
> > > need to use simics 3. 
> > >
> > > Thank you for your help.
> > >
> > >   
> > >       
> > > > Carles,
> > > >   
> > > > I looked into things, and made a mistake in answering your question. 
> > > > There is no longer an explicit SIMICS_VERSION flag in the module 
> > > > makefiles of Gems 1.3. There *IS*, however, a path that must be set 
> > > > appropriately for Simics 3.0, which specifies the Makefile's GEMS_ROOT 
> > > > variable. Can you please verify that your ruby/module/Makefile has 
> > > > GEMS_ROOT set to $(SRC_BASE)/../../ ?
> > > > (then make clean and build again)
> > > >
> > > > Regards,
> > > > Dan
> > > >
> > > > Dan Gibson wrote:
> > > >   
> > > >
> > > >     I think this changed in GEMS 1.4 ... I could be wrong. When I
> > > >     initially ported GEMS to Simics 3, my port had a flag in
> > > >     ruby/module/Makefile -- that may have disappeared.
> > > >
> > > >     Daniel Nussbaum - Sun Microsystems - Burlington United States wrote:
> > > >         
> > > >
> > > >         I'm pretty sure that the only place that SIMICS_VERSION needs to be
> > > >         set is in
> > > >
> > > >           common/Makefile.simics_version
> > > >
> > > >         (This is different from what Carles said that he did.)
> > > >
> > > >         dann
> > > >
> > > >               
> > > >
> > > >             Date: Fri, 07 Sep 2007 09:57:27 -0500
> > > >             From: Dan Gibson <degibson@xxxxxxxx>
> > > >
> > > >             As I recall, there is another flag that must be set in ruby/module/Makefile.
> > > >
> > > >             Regards,
> > > >             Dan
> > > >
> > > >             Carles Hernández wrote:
> > > >                     
> > > >
> > > >                 Thank you Dan for your answer.
> > > >                 I have set the SIMICS_VERSION flag to 3.0 in $GEMS/common/Makefile.common.
> > > >                 Did you mean this flag?
> > > >
> > > >                           
> > > >
> > > >         _______________________________________________
> > > >         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/"; <https://lists.cs.wisc.edu/archive/gems-users/%22>; to your search.
> > > >
> > > >               
> > > >
> > > >     
> > > >         
> > > _______________________________________________
> > > 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.
> > >
> > >
> > >   
> > >       
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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.
> >
> >   
> >     
> _______________________________________________
> 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.
>
>   
--
http://www.cs.wisc.edu/~gibson [esc]:wq!