No, there is no -Werror option in SConstruct :(

On Tue, Dec 27, 2011 at 3:39 PM, Mahmood Naderan <[email protected]>wrote:

> Do you have any "-Werror" option in gem5/SConstruct?
> if yes, remove that.
>
> On 12/27/11, Muhammet ÖZGÜR <[email protected]> wrote:
> > Thank you for your answer...
> >
> > But again I got error..
> > I googled it but I could not find anything.
> > What should I do now?
> > Thank you...
> > ...
> >  [ SO SWIG] Process -> ARM_SE/python/m5/internal/param_Process.i
> >  [ SO SWIG] System -> ARM_SE/python/m5/internal/param_System.i
> >  [ENUMSWIG] MemoryMode -> ARM_SE/python/m5/internal/enum_MemoryMode.i
> >  [    SWIG] ARM_SE/python/m5/internal/Process_vector.i -> _wrap.cc, .py
> >  [     CXX] ARM_SE/python/m5/internal/Process_vector_wrap.cc -> .o
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc: In function
> > 'std::vector<Process*, std::allocator<Process*> >*
> > std_vector_Sl_Process_Sm__Sg____getitem____SWIG_0(std::vector<Process*,
> > std::allocator<Process*> >*, PySliceObject*)':
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc:4398:48: error:
> > 'SWIGPY_SLICE_ARG' was not declared in this scope
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc: In function 'void
> > std_vector_Sl_Process_Sm__Sg____setitem____SWIG_0(std::vector<Process*,
> > std::allocator<Process*> >*, PySliceObject*, const std::vector<Process*,
> > std::allocator<Process*> >&)':
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc:4407:48: error:
> > 'SWIGPY_SLICE_ARG' was not declared in this scope
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc: In function 'void
> > std_vector_Sl_Process_Sm__Sg____setitem____SWIG_1(std::vector<Process*,
> > std::allocator<Process*> >*, PySliceObject*)':
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc:4416:48: error:
> > 'SWIGPY_SLICE_ARG' was not declared in this scope
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc: In function 'void
> > std_vector_Sl_Process_Sm__Sg____delitem____SWIG_1(std::vector<Process*,
> > std::allocator<Process*> >*, PySliceObject*)':
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc:4425:48: error:
> > 'SWIGPY_SLICE_ARG' was not declared in this scope
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc: In function
> > 'PyObject* _wrap_new_vector_Process__SWIG_0(PyObject*, PyObject*)':
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc:5360:1: warning:
> > label 'fail' defined but not used
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc: At global scope:
> > build/ARM_SE/python/m5/internal/Process_vector_wrap.cc:916:13: warning:
> > 'long int PyNumber_AsSsize_t(PyObject*, void*)' defined but not used
> > scons: *** [build/ARM_SE/python/m5/internal/Process_vector_wrap.o] Error
> 1
> > scons: building terminated because of errors.
> >
> >
> > On Tue, Dec 27, 2011 at 2:59 PM, Iordan Alexandru <[email protected]>
> wrote:
> >
> >> Hello
> >>
> >> A very simple fix would be to disable the warnings for scons. You can do
> >> this by editing the SConscript file in the  src folder. Change the
> >> "Werror = true" to "Werror=false" and comment
> >> "swig_env.Append(CCFLAGS='-Werror').
> >>
> >> Hope this works.
> >>
> >> Happy holidays!
> >> Alexandru
> >>
> >>   ------------------------------
> >> *From:* Muhammet ÖZGÜR <[email protected]>
> >> *To:* [email protected]
> >> *Sent:* Tuesday, December 27, 2011 1:15 PM
> >> *Subject:* [gem5-users] GEM5 Build error
> >>
> >> Hi,
> >>
> >> I'm trying to build gem5. I wrote to  terminal   'scons
> >> build/ARM_SE/gem5.opt'  and i got the error as below:
> >>
> >>  ...
> >>  [     CXX] ARM_SE/mem/ruby/network/orion/Allocator/SWAllocator.cc ->
> .do
> >>  [     CXX] ARM_SE/mem/ruby/network/orion/Allocator/VCAllocator.cc ->
> .do
> >>  [     CXX] ARM_SE/mem/ruby/network/simple/PerfectSwitch.cc -> .do
> >>  [     CXX] ARM_SE/mem/ruby/network/simple/SimpleLink.cc -> .do
> >>  [     CXX] ARM_SE/mem/ruby/network/simple/SimpleNetwork.cc -> .do
> >>  [     CXX] ARM_SE/mem/ruby/network/simple/Switch.cc -> .do
> >>  [     CXX] ARM_SE/mem/ruby/network/simple/Throttle.cc -> .do
> >>  [     CXX] ARM_SE/python/swig/pyevent.cc -> .do
> >>  [     CXX] ARM_SE/python/swig/pyobject.cc -> .do
> >>  [     CXX] ARM_SE/python/swig/core_wrap.cc -> .do
> >> cc1plus: warnings being treated as errors
> >> build/ARM_SE/python/swig/core_wrap.cc: In function 'PyObject*
> >> _wrap_doExitCleanup(PyObject*, PyObject*)':
> >> build/ARM_SE/python/swig/core_wrap.cc:3721:1: error: label 'fail'
> defined
> >> but not used
> >> build/ARM_SE/python/swig/core_wrap.cc: In function 'PyObject*
> >> _wrap_disableAllListeners(PyObject*, PyObject*)':
> >> build/ARM_SE/python/swig/core_wrap.cc:3732:1: error: label 'fail'
> defined
> >> but not used
> >> build/ARM_SE/python/swig/core_wrap.cc: In function 'PyObject*
> >> _wrap_curTick(PyObject*, PyObject*)':
> >> build/ARM_SE/python/swig/core_wrap.cc:3842:1: error: label 'fail'
> defined
> >> but not used
> >> build/ARM_SE/python/swig/core_wrap.cc: At global scope:
> >> build/ARM_SE/python/swig/core_wrap.cc:916:13: error: 'long int
> >> PyNumber_AsSsize_t(PyObject*, void*)' defined but not used
> >> scons: *** [build/ARM_SE/python/swig/core_wrap.do] Error 1
> >> scons: building terminated because of errors.
> >>
> >>
> >> How can I fix this?
> >>
> >> thank you...
> >>
> >>
> >> ---
> >> Muhammet OZGUR
> >> Kasirga Microprocessors Lab.
> >> Research Assistant
> >>
> >> _______________________________________________
> >> 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
> >>
> >
>
>
> --
> --
> // Naderan *Mahmood;
> _______________________________________________
> 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