Re: [Gems-users] GEMS release 1.3 compiling error

["Lei Yang" <lya755@xxxxxxxxxxxxxxxxxxxx>]

Hi Derin,

Thanks for the help! When I look into the simics_3_workspace, there is 
already x86-linux/obj . So I guess the problems I encountered are not 
exactly the same as yours. But as you said, I did have some header file 
missings (complaining about a global.h ). So I searched in simics directory 
and found that file is right in $SIMICS_CORE/src/include/obsolete/global.h . 
So I modified ruby/Makefile
ifeq ($(SIMICS_VERSION),3.0)
 SIMICS_INCLUDE_ROOT = /opt/virtutech/simics-3.0.4/src/include
 INCLUDES  = -I$(SIMICS_INCLUDE_ROOT)
 INCLUDES += -I$(SIMICS_INCLUDE_ROOT)/simics
 INCLUDES += -I$(SIMICS_INCLUDE_ROOT)/simics/core
 INCLUDES += -I$(SIMICS_INCLUDE_ROOT)/simics/arch
 INCLUDES += -I$(SIMICS_INCLUDE_ROOT)/simics/util

Although this line SIMICS_INCLUDE_ROOT = 
/opt/virtutech/simics-3.0.4/src/include  I already defined in 
gems/common/Makefile.common
But thanks for your reply anyway!

Lei
----- Original Message ----- 
From: <mehmetderin.harmanci@xxxxxxx>
To: "Gems Users" <gems-users@xxxxxxxxxxx>
Sent: Thursday, August 24, 2006 7:22 AM
Subject: Re: [Gems-users] GEMS release 1.3 compiling error


>  Hello,
>
>   I had run into a similar problem when compiling ruby I guess. Initially
>  My problem was different, some header files were missing so I had changed
>  the simics link to point to the SIMICS directory (where the core of 
> simics,
>  as well as its documentation its source extensions are ). But when I did
>  this I remember having a similar problem as yours. I do not know if you
>  did such a manipulation of links by hand. If so I'll advise you to read
>  the content of the file I wrote for myself in case I recompile gems in 
> the
>  future, whihc I copy below (however, this may require you to restart the
>  gems installation from scracth :( ) Here is the file content:
>
>
> After doing all setup details that is explained as in the web page
>
> http://www.cs.wisc.edu/gems/doc/wiki/moin.cgi/Setup_for_Simics_3.0.X
>
>
> One more thing needs also to be done (at least that how I managed):
>
> cd $GEMS/simic_3_workspace
> mkdir x86-linux
> mkdir x86-linux/obj
> cp -r $SIMICS-CORE/src/include x86-linux/obj
>
> Here $SIMIC_CORE points to the directory where simics installation is done
> and the source code is. IT IS NOT A WORKSPACE DIRECTORY. This last lines
> are necessary because gems modules require the some headers that are in
> the created simics workspace directory (simics_3_workspace). However the
> scripts they provide do not copy the include directory to this workspace
> directory.
>
> Once this is done everything works fine.
>
>
>    Hope this helps,
>
>        Derin.
>
>
>
> Quoting lya755@xxxxxxxxxxxxxxxxxxxx:
>
> > Hi list,
> >
> > I am trying to setup GEMS release 1.3 with Simics 3.0.4. I followed the
> > instructions on
> > http://www.cs.wisc.edu/gems/doc/wiki/moin.cgi/Setup_for_Simics_3.0.X
> >
> > However, compiling ruby gives me the following error after seeing a lot 
> > of
> > stuff on the screen:
> >
> > touch x86-linux/generated/MOSI_SMP_bcast/bin/ruby.closure
> > Template closure done
> > Made module
> > make[1]: Leaving directory `/newhd2/gems/ruby'
> > Ruby: Linking simics module
> > cd ../simics; make ruby
> > make[1]: Entering directory `/newhd2/gems/simics_3_workspace'
> > make[2]: Entering directory `/newhd2/gems/simics_3_workspace/x86-
> > linux/obj/modules/ruby'
> > make[2]: *** No rule to make target `ruby.o', needed by
> > `/newhd2/gems/simics_3_workspace/x86-linux/lib/ruby.so'.  Stop.
> > make[2]: Leaving directory `/newhd2/gems/simics_3_workspace/x86-
> > linux/obj/modules/ruby'
> > make[1]: *** [ruby] Error 2
> > make[1]: Leaving directory `/newhd2/gems/simics_3_workspace'
> > make: *** [all] Error 2
> >
> > Similarly, compiling opal gives me this error:
> >
> > make[1]: Leaving directory `/newhd2/gems/opal'
> > Opal: Linking simics module
> > cd ../simics; make opal
> > make[1]: Entering directory `/newhd2/gems/simics_3_workspace'
> > make[2]: Entering directory `/newhd2/gems/simics_3_workspace/x86-
> > linux/obj/modules/opal'
> >         module_id.c
> > DEP     module_id.d
> > make[2]: Leaving directory `/newhd2/gems/simics_3_workspace/x86-
> > linux/obj/modules/opal'
> > make[2]: Entering directory `/newhd2/gems/simics_3_workspace/x86-
> > linux/obj/modules/opal'
> > make[2]: *** No rule to make target `opal.o', needed by
> > `/newhd2/gems/simics_3_workspace/x86-linux/lib/opal.so'.  Stop.
> > make[2]: Leaving directory `/newhd2/gems/simics_3_workspace/x86-
> > linux/obj/modules/opal'
> > make[1]: *** [opal] Error 2
> > make[1]: Leaving directory `/newhd2/gems/simics_3_workspace'
> > make: *** [module] Error 2
> >
> >
> > I'd appreciate if somebody could give me a hint on how to get over this.
> > Thanks in advance!!
> >
> > Lei
> >
> > _________________________________________________________
> > This message was sent through the NU ECE webmail gateway.
> > _______________________________________________
> > 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.