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]> 
> 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]>:
> 
> 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 for reporting bugs and further information
> 
> Regards,
> Digant Desai.
> 
> 
> 
> On Wed, Sep 28, 2011 at 11:45, Gabe Black <[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]> 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]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
> 
> 
> 
> _______________________________________________
> gem5-users mailing 
> [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
> 
> _______________________________________________
> 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

Reply via email to