Did you delete your whole build directory and rebuild everything? You may have stale files from previous versions of the tools.
Gabe On 09/28/11 19:15, Digant wrote: > I changed it to 2.0.3 but now compilation finishes with this message > > [ SHCC] libelf/libelf_data.c -> .os > [ SHCC] libelf/libelf_ehdr.c -> .os > [ SHCC] libelf/libelf_extended.c -> .os > [ SHCC] libelf/libelf_phdr.c -> .os > [ SHCC] libelf/libelf_shdr.c -> .os > [ SHCC] libelf/libelf_xlate.c -> .os > [ SHCC] libelf/libelf_convert.c -> .os > [ SHCC] libelf/libelf_fsize.c -> .os > [ SHCC] libelf/libelf_msize.c -> .os > [ SHCXX] gzstream/gzstream.cc -> .os > [ LINK] -> ARM_FS/gem5.debug > /usr/local/lib/libpython2.7.a(posixmodule.o): In function `posix_tmpnam': > /home/salvador/preDoc/ad11/gem5/Python-2.7.2/./Modules/posixmodule.c:7370: > warning: the use of `tmpnam_r' is dangerous, better use `mkstemp' > /usr/local/lib/libpython2.7.a(posixmodule.o): In function `posix_tempnam': > /home/salvador/preDoc/ad11/gem5/Python-2.7.2/./Modules/posixmodule.c:7317: > warning: the use of `tempnam' is dangerous, better use `mkstemp' > scons: done building targets. > > but when I try to tun gem5 this is the error... > > root@PUMA:/home/guest/GEM5/gem5-stable# build/ARM_FS/gem5.debug > Traceback (most recent call last): > File "<string>", line 1, in <module> > AttributeError: 'module' object has no attribute 'main' > root@PUMA:/home/guest/GEM5/gem5-stable# > > > > Regards, > Digant Desai. > > > > On Wed, Sep 28, 2011 at 15:59, Ali Saidi <[email protected] > <mailto:[email protected]>> wrote: > > This is getting ridiculous. There are like 4 versions of SWIG that > work now. We really need to figure out why 2.0.4 is broken. > > Ali > > On Sep 28, 2011, at 8:31 PM, Digant wrote: > >> ok thank you for quick reply, >> I have 1.3.40 also and I can install 2.0.3 , I ve checked >> SConstruct file but I didnt get how to tell GEM5 to use >> particular version of swig ? >> >> Regards, >> Digant Desai. >> >> >> >> On Wed, Sep 28, 2011 at 12:25, Gabriel Michael Black >> <[email protected] <mailto:[email protected]>> wrote: >> >> Not 2.0.4, 2.0.3. It doesn't seem like there should be a >> difference, but there is. >> >> Gabe >> >> >> Quoting Digant <[email protected] >> <mailto:[email protected]>>: >> >> still same problem, >> >> terminal :~$ swig -version >> >> SWIG Version 2.0.4 >> >> Compiled with g++ [i686-pc-linux-gnu] >> >> Configured options: +pcre >> >> Please see http://www.swig.org <http://www.swig.org/> for >> reporting bugs and further information >> >> Regards, >> Digant Desai. >> >> >> >> On Wed, Sep 28, 2011 at 11:45, Gabe Black >> <[email protected] <mailto:[email protected]>> wrote: >> >> ** >> Please try swig version 2.0.3. >> >> Gabe >> >> >> On 09/28/11 10:31, Digant wrote: >> >> Thank you nilay for quick reply, >> >> terminal :~$ swig -version >> SWIG Version 1.3.40 >> Compiled with g++ [i686-pc-linux-gnu] >> >> Regards, >> Digant Desai. >> >> >> >> On Wed, Sep 28, 2011 at 10:29, Nilay Vaish >> <[email protected] <mailto:[email protected]>> wrote: >> >> On Wed, 28 Sep 2011, Digant wrote: >> >> I am getting this error when I am trying to >> compile stable version for >> >> ARM_FS.. >> . >> . >> . >> [ENUMSWIG] OpClass -> >> ARM_FS/python/m5/internal/enum_OpClass.i >> [BLDPARAM] SimObject -> >> ARM_FS/python/m5/internal/param_SimObject.i >> [ SWIG] >> ARM_FS/python/m5/internal/vptype_OpDesc.i -> >> _wrap.cc, .py >> [ CXX] >> ARM_FS/python/m5/internal/vptype_OpDesc_wrap.cc >> -> .do >> [SW PARAM] AddrRange -> >> ARM_FS/python/m5/internal/vptype_AddrRange.i >> [ SWIG] >> ARM_FS/python/m5/internal/vptype_AddrRange.i >> -> _wrap.cc, .py >> [ CXX] >> ARM_FS/python/m5/internal/vptype_AddrRange_wrap.cc >> -> .do >> [SW PARAM] IdeDisk -> >> ARM_FS/python/m5/internal/vptype_IdeDisk.i >> [BLDPARAM] IdeDisk -> >> ARM_FS/python/m5/internal/param_IdeDisk.i >> [ENUMSWIG] IdeID -> >> ARM_FS/python/m5/internal/enum_IdeID.i >> [BLDPARAM] DiskImage -> >> ARM_FS/python/m5/internal/param_DiskImage.i >> [ SWIG] >> ARM_FS/python/m5/internal/vptype_IdeDisk.i -> >> _wrap.cc, .py >> [ CXX] >> ARM_FS/python/m5/internal/vptype_IdeDisk_wrap.cc >> -> .do >> [SW PARAM] FUDesc -> >> ARM_FS/python/m5/internal/vptype_FUDesc.i >> [BLDPARAM] FUDesc -> >> ARM_FS/python/m5/internal/param_FUDesc.i >> [ SWIG] >> ARM_FS/python/m5/internal/vptype_FUDesc.i -> >> _wrap.cc, .py >> [ CXX] >> ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc >> -> .do >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc: >> In function >> 'std::vector<FUDesc*, std::allocator<FUDesc*> >* >> >> std_vector_Sl_FUDesc_Sm__Sg____getitem____SWIG_0(std::vector<FUDesc*, >> std::allocator<FUDesc*> >*, PySliceObject*)': >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc:4398:48: >> error: >> 'SWIGPY_SLICE_ARG' was not declared in this scope >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc: >> In function 'void >> >> std_vector_Sl_FUDesc_Sm__Sg____setitem____SWIG_0(std::vector<FUDesc*, >> std::allocator<FUDesc*> >*, PySliceObject*, >> const std::vector<FUDesc*, >> std::allocator<FUDesc*> >&)': >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc:4407:48: >> error: >> 'SWIGPY_SLICE_ARG' was not declared in this scope >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc: >> In function 'void >> >> std_vector_Sl_FUDesc_Sm__Sg____setitem____SWIG_1(std::vector<FUDesc*, >> std::allocator<FUDesc*> >*, PySliceObject*)': >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc:4416:48: >> error: >> 'SWIGPY_SLICE_ARG' was not declared in this scope >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc: >> In function 'void >> >> std_vector_Sl_FUDesc_Sm__Sg____delitem____SWIG_1(std::vector<FUDesc*, >> std::allocator<FUDesc*> >*, PySliceObject*)': >> >> build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.cc:4425:48: >> error: >> 'SWIGPY_SLICE_ARG' was not declared in this scope >> scons: *** >> >> [build/ARM_FS/python/m5/internal/vptype_FUDesc_wrap.do] >> Error >> 1 >> scons: building terminated because of errors. >> >> >> >> Digant, this seems like a swig error. Which swig >> version are you using? >> >> -- >> Nilay >> _______________________________________________ >> gem5-users mailing list >> [email protected] <mailto:[email protected]> >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >> >> >> _______________________________________________ >> gem5-users mailing >> >> [email protected]http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> <http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users> >> >> >> >> >> _______________________________________________ >> gem5-users mailing list >> [email protected] <mailto:[email protected]> >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >> >> >> >> _______________________________________________ >> gem5-users mailing list >> [email protected] <mailto:[email protected]> >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >> >> _______________________________________________ >> gem5-users mailing list >> [email protected] <mailto:[email protected]> >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > _______________________________________________ > gem5-users mailing list > [email protected] <mailto:[email protected]> > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
