[gem5-users] gem5 build error with gcc-9.2.1

[Anuj Falcon]

Though I switched back to gcc-7.4 to get the job done, I faced the error
message below while building with gcc-9.2.1 in Ubuntu 19.10.

In file included from build/RISCV/cpu/base.hh:64,
 from build/RISCV/kern/linux/events.cc:51:
build/RISCV/sim/insttracer.hh: In member function 'void
Trace::InstRecord::setData(VecRegContainer<8>&)':
build/RISCV/sim/insttracer.hh:203:71: *error: implicitly-declared
'constexpr VecRegContainer<8>::VecRegContainer(const VecRegContainer<8>&)'
is deprecated [-Werror=deprecated-copy]*
  203 | data.as_vec = new
::VecRegContainer(d);

-- 
-
J ANUJ
-
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] Gem5 build error

[Jason Lowe-Power]

Hi Thawra,

Here's another patch:
https://gem5-review.googlesource.com/c/public/gem5/+/11949. I would greatly
appreciate it if you created an account on gem5-review.googlesource.com and
made comments/reviewed the patches there. If you have any questions on how
to do that, please let me know off list.

Thanks,
Jason

On Tue, Jul 31, 2018 at 10:17 AM Thawra Kadeed 
wrote:

> Hi Jason,
>
> thanks for your quick answer.
>
> I downloaded the pybind11 from
> https://github.com/pybind/pybind11/pull/1396
> ,removed the old one and used this one, then complied but I got another
> error after the past error passed:
>
> New result:
>
> scons: Building targets ...
>   [ CXX] ARM/sim/main.cc -> .o
>   [ CXX] ARM/mem/ruby/filters/BlockBloomFilter.cc -> .o
> In file included from build/ARM/sim/serialize.hh:61,
>   from build/ARM/sim/eventq.hh:53,
>   from build/ARM/sim/core.hh:44,
>   from build/ARM/mem/request.hh:62,
>   from build/ARM/mem/packet.hh:66,
>   from build/ARM/mem/ruby/system/RubySystem.hh:40,
>   from build/ARM/mem/ruby/filters/BlockBloomFilter.cc:33:
>
> build/ARM/base/bitunion.hh: In function 'std::ostream&
> BitfieldBackend::bitfieldBackendPrinter(std::ostream&, const T&) [with T
> = char; std::ostream = std::basic_ostream]':
> build/ARM/base/bitunion.hh:438:26: ERROR: type qualifiers ignored on
> cast result type [-Werror=ignored-qualifiers]
>   os << (const int)t;
>^
> build/ARM/base/bitunion.hh: In function 'std::ostream&
> BitfieldBackend::bitfieldBackendPrinter(std::ostream&, const T&) [with T
> = unsigned char; std::ostream = std::basic_ostream]':
> build/ARM/base/bitunion.hh:446:35: ERROR: type qualifiers ignored on
> cast result type [-Werror=ignored-qualifiers]
>   os << (const unsigned int)t;
>
>
> Is it also because of gcc8?
> Thanks again,
> Thawra
>
>
> On 2018-07-31 18:27, Jason Lowe-Power wrote:
> > Hi Thawra,
> >
> > It looks like this pybind11 commit fixes the issue.
> > https://github.com/pybind/pybind11/pull/1396. Last time you sent the
> > email no one had posted a fix to pybind, yet :).
> >
> > I just posted a patch on gerrit. Please download it, test it, and
> > review it on gerrit. If it works for you we'll push it into mainline.
> > https://gem5-review.googlesource.com/c/public/gem5/+/11909
> >
> > Cheers,
> > Jason
> >
> > On Tue, Jul 31, 2018 at 9:08 AM Thawra Kadeed
> >  wrote:
> >
> >> Hello Jason,
> >>
> >> I submitted before this error message I got during the build process
> >> of
> >> Gem5.
> >>
> >> you recommended me either to use previous versions of gcc (e.g. gcc
> >> 7)
> >> or to use clang.
> >>
> >> As I am using Feodra28, I am not able to install gcc 7 because there
> >> are
> >> no corresponding dependencies in fedora28 for such a version.
> >> However, I removed gcc8 and installed clang. Here, gcc8 installs
> >> automatically as a dependency package for clang. I tried to build, I
> >> got
> >> the same error.
> >>
> >> I do not know which c compiler the scons uses. I tried to look if I
> >> am
> >> able to specify the c compiler in the scons but have not seen such a
> >>
> >> choice.
> >>
> >> Could anyone please give me a hint about this problem.
> >> Thanks in advance,
> >> Thawra
> >>
> >> PS: your old answer was:
> >> Hi Thawra,
> >>
> >> My guess is that this is an issue with the version of pybind11
> >> we're
> >> using
> >> and gcc 8+. We haven't tested on anything after gcc 7.X.
> >>
> >> I'll put testing gcc 8 on my to do list, but I don't know when
> >> I'll get
> >> to
> >> it. I would try downgrading gcc to 7 or possibly using clang.
> >>
> >> jason
> >>
> >> On 2018-05-08 18:46, thaw...@ida.ing.tu-bs.de wrote:
> >>> Hello,
> >>>
> >>> I am Thawra Kadeed from the university of Braunschweig in Germany.
> >>>
> >>> I started using Gem5 and during the build process I got the
> >> foolowing
> >>> error:
> >>>
> >>> ext/pybind11/include/pybind11/pybind11.h: In member function 'void
> >>>
> >>
> >
> pybind11::cpp_function::initialize_generic(pybind11::detail::function_record*,
> >>> const char*, const std::type_info* const*, pybind11::size_t)':
> >>> ext/pybind11/include/pybind11/pybind11.h:320:74: error: cast
> >> between
> >>> incompatible function types from 'PyObject* (*)(PyObject*,
> >> PyObject*,
> >>> PyObject*)' {aka '_object* (*)(_object*, _object*, _object*)'} to
> >>> 'PyCFunction' {aka '_object* (*)(_object*, _object*)'}
> >>> [-Werror=cast-function-type]
> >>> rec->def->ml_meth =
> >>> reinterpret_cast(*dispatcher);
> >>>
> >>>
> >>> Obviously as the error reports that the problem is cast between
> >>> incompatible function types from 'PyObject' to 'PyCFunction'
> >>>
> >>> I installed all the required dependencies and as I am using
> >> fedora28 I
> >>> installed:
> >>>
> >>> Python 2.7.14 and gcc-8.0.1-0.20.fc28.x86_64
> >>>
> >>> I hope you have a helpful guide in this issue.
> >>> Thanks in 

Re: [gem5-users] Gem5 build error

[Thawra Kadeed]

Hi Jason,

thanks for your quick answer.

I downloaded the pybind11 from 
https://github.com/pybind/pybind11/pull/1396
,removed the old one and used this one, then complied but I got another 
error after the past error passed:


New result:

scons: Building targets ...
 [ CXX] ARM/sim/main.cc -> .o
 [ CXX] ARM/mem/ruby/filters/BlockBloomFilter.cc -> .o
In file included from build/ARM/sim/serialize.hh:61,
 from build/ARM/sim/eventq.hh:53,
 from build/ARM/sim/core.hh:44,
 from build/ARM/mem/request.hh:62,
 from build/ARM/mem/packet.hh:66,
 from build/ARM/mem/ruby/system/RubySystem.hh:40,
 from build/ARM/mem/ruby/filters/BlockBloomFilter.cc:33:

build/ARM/base/bitunion.hh: In function 'std::ostream& 
BitfieldBackend::bitfieldBackendPrinter(std::ostream&, const T&) [with T 
= char; std::ostream = std::basic_ostream]':
build/ARM/base/bitunion.hh:438:26: ERROR: type qualifiers ignored on 
cast result type [-Werror=ignored-qualifiers]

 os << (const int)t;
  ^
build/ARM/base/bitunion.hh: In function 'std::ostream& 
BitfieldBackend::bitfieldBackendPrinter(std::ostream&, const T&) [with T 
= unsigned char; std::ostream = std::basic_ostream]':
build/ARM/base/bitunion.hh:446:35: ERROR: type qualifiers ignored on 
cast result type [-Werror=ignored-qualifiers]

 os << (const unsigned int)t;


Is it also because of gcc8?
Thanks again,
Thawra


On 2018-07-31 18:27, Jason Lowe-Power wrote:

Hi Thawra,

It looks like this pybind11 commit fixes the issue.
https://github.com/pybind/pybind11/pull/1396. Last time you sent the
email no one had posted a fix to pybind, yet :).

I just posted a patch on gerrit. Please download it, test it, and
review it on gerrit. If it works for you we'll push it into mainline.
https://gem5-review.googlesource.com/c/public/gem5/+/11909

Cheers,
Jason

On Tue, Jul 31, 2018 at 9:08 AM Thawra Kadeed
 wrote:


Hello Jason,

I submitted before this error message I got during the build process
of
Gem5.

you recommended me either to use previous versions of gcc (e.g. gcc
7)
or to use clang.

As I am using Feodra28, I am not able to install gcc 7 because there
are
no corresponding dependencies in fedora28 for such a version.
However, I removed gcc8 and installed clang. Here, gcc8 installs
automatically as a dependency package for clang. I tried to build, I
got
the same error.

I do not know which c compiler the scons uses. I tried to look if I
am
able to specify the c compiler in the scons but have not seen such a

choice.

Could anyone please give me a hint about this problem.
Thanks in advance,
Thawra

PS: your old answer was:
Hi Thawra,

My guess is that this is an issue with the version of pybind11
we're
using
and gcc 8+. We haven't tested on anything after gcc 7.X.

I'll put testing gcc 8 on my to do list, but I don't know when
I'll get
to
it. I would try downgrading gcc to 7 or possibly using clang.

jason

On 2018-05-08 18:46, thaw...@ida.ing.tu-bs.de wrote:

Hello,

I am Thawra Kadeed from the university of Braunschweig in Germany.

I started using Gem5 and during the build process I got the

foolowing

error:

ext/pybind11/include/pybind11/pybind11.h: In member function 'void




pybind11::cpp_function::initialize_generic(pybind11::detail::function_record*,

const char*, const std::type_info* const*, pybind11::size_t)':
ext/pybind11/include/pybind11/pybind11.h:320:74: error: cast

between

incompatible function types from 'PyObject* (*)(PyObject*,

PyObject*,

PyObject*)' {aka '_object* (*)(_object*, _object*, _object*)'} to
'PyCFunction' {aka '_object* (*)(_object*, _object*)'}
[-Werror=cast-function-type]
rec->def->ml_meth =
reinterpret_cast(*dispatcher);


Obviously as the error reports that the problem is cast between
incompatible function types from 'PyObject' to 'PyCFunction'

I installed all the required dependencies and as I am using

fedora28 I

installed:

Python 2.7.14 and gcc-8.0.1-0.20.fc28.x86_64

I hope you have a helpful guide in this issue.
Thanks in advance.
Best regards,
Thawra

___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] Gem5 build error

[Jason Lowe-Power]

Hi Thawra,

It looks like this pybind11 commit fixes the issue.
https://github.com/pybind/pybind11/pull/1396. Last time you sent the email
no one had posted a fix to pybind, yet :).

I just posted a patch on gerrit. Please download it, test it, and review it
on gerrit. If it works for you we'll push it into mainline.
https://gem5-review.googlesource.com/c/public/gem5/+/11909

Cheers,
Jason

On Tue, Jul 31, 2018 at 9:08 AM Thawra Kadeed 
wrote:

> Hello Jason,
>
> I submitted before this error message I got during the build process of
> Gem5.
>
> you recommended me either to use previous versions of gcc (e.g. gcc 7)
> or to use clang.
>
> As I am using Feodra28, I am not able to install gcc 7 because there are
> no corresponding dependencies in fedora28 for such a version.
> However, I removed gcc8 and installed clang. Here, gcc8 installs
> automatically as a dependency package for clang. I tried to build, I got
> the same error.
>
> I do not know which c compiler the scons uses. I tried to look if I am
> able to specify the c compiler in the scons but have not seen such a
> choice.
>
> Could anyone please give me a hint about this problem.
> Thanks in advance,
> Thawra
>
> PS: your old answer was:
>   Hi Thawra,
>
>   My guess is that this is an issue with the version of pybind11 we're
> using
>   and gcc 8+. We haven't tested on anything after gcc 7.X.
>
>   I'll put testing gcc 8 on my to do list, but I don't know when I'll get
> to
>   it. I would try downgrading gcc to 7 or possibly using clang.
>
> jason
>
>
> On 2018-05-08 18:46, thaw...@ida.ing.tu-bs.de wrote:
> > Hello,
> >
> > I am Thawra Kadeed from the university of Braunschweig in Germany.
> >
> > I started using Gem5 and during the build process I got the foolowing
> > error:
> >
> > ext/pybind11/include/pybind11/pybind11.h: In member function 'void
> >
> pybind11::cpp_function::initialize_generic(pybind11::detail::function_record*,
> > const char*, const std::type_info* const*, pybind11::size_t)':
> > ext/pybind11/include/pybind11/pybind11.h:320:74: error: cast between
> > incompatible function types from 'PyObject* (*)(PyObject*, PyObject*,
> > PyObject*)' {aka '_object* (*)(_object*, _object*, _object*)'} to
> > 'PyCFunction' {aka '_object* (*)(_object*, _object*)'}
> > [-Werror=cast-function-type]
> >  rec->def->ml_meth =
> > reinterpret_cast(*dispatcher);
> >
> >
> > Obviously as the error reports that the problem is cast between
> > incompatible function types from 'PyObject' to 'PyCFunction'
> >
> > I installed all the required dependencies and as I am using fedora28 I
> > installed:
> >
> > Python 2.7.14 and gcc-8.0.1-0.20.fc28.x86_64
> >
> > I hope you have a helpful guide in this issue.
> > Thanks in advance.
> > Best regards,
> > Thawra
>
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] Gem5 build error

[Thawra Kadeed]

Hello Jason,

I submitted before this error message I got during the build process of 
Gem5.


you recommended me either to use previous versions of gcc (e.g. gcc 7) 
or to use clang.


As I am using Feodra28, I am not able to install gcc 7 because there are 
no corresponding dependencies in fedora28 for such a version.
However, I removed gcc8 and installed clang. Here, gcc8 installs 
automatically as a dependency package for clang. I tried to build, I got 
the same error.


I do not know which c compiler the scons uses. I tried to look if I am 
able to specify the c compiler in the scons but have not seen such a 
choice.


Could anyone please give me a hint about this problem.
Thanks in advance,
Thawra

PS: your old answer was:
 Hi Thawra,

 My guess is that this is an issue with the version of pybind11 we're 
using

 and gcc 8+. We haven't tested on anything after gcc 7.X.

 I'll put testing gcc 8 on my to do list, but I don't know when I'll get 
to

 it. I would try downgrading gcc to 7 or possibly using clang.

jason


On 2018-05-08 18:46, thaw...@ida.ing.tu-bs.de wrote:

Hello,

I am Thawra Kadeed from the university of Braunschweig in Germany.

I started using Gem5 and during the build process I got the foolowing 
error:


ext/pybind11/include/pybind11/pybind11.h: In member function 'void
pybind11::cpp_function::initialize_generic(pybind11::detail::function_record*,
const char*, const std::type_info* const*, pybind11::size_t)':
ext/pybind11/include/pybind11/pybind11.h:320:74: error: cast between
incompatible function types from 'PyObject* (*)(PyObject*, PyObject*,
PyObject*)' {aka '_object* (*)(_object*, _object*, _object*)'} to
'PyCFunction' {aka '_object* (*)(_object*, _object*)'}
[-Werror=cast-function-type]
 rec->def->ml_meth = 
reinterpret_cast(*dispatcher);



Obviously as the error reports that the problem is cast between
incompatible function types from 'PyObject' to 'PyCFunction'

I installed all the required dependencies and as I am using fedora28 I
installed:

Python 2.7.14 and gcc-8.0.1-0.20.fc28.x86_64

I hope you have a helpful guide in this issue.
Thanks in advance.
Best regards,
Thawra

___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] Gem5 build error

[Jason Lowe-Power]

Hi Thawra,

My guess is that this is an issue with the version of pybind11 we're using
and gcc 8+. We haven't tested on anything after gcc 7.X.

I'll put testing gcc 8 on my to do list, but I don't know when I'll get to
it. I would try downgrading gcc to 7 or possibly using clang.

Jason

On Tue, May 8, 2018 at 10:02 AM  wrote:

> Hello,
>
> I am Thawra Kadeed from the university of Braunschweig in Germany.
>
> I started using Gem5 and during the build process I got the foolowing
> error:
>
> ext/pybind11/include/pybind11/pybind11.h: In member function 'void
> pybind11::cpp_function::initialize_generic(pybind11::detail::function_record*,
>
> const char*, const std::type_info* const*, pybind11::size_t)':
> ext/pybind11/include/pybind11/pybind11.h:320:74: error: cast between
> incompatible function types from 'PyObject* (*)(PyObject*, PyObject*,
> PyObject*)' {aka '_object* (*)(_object*, _object*, _object*)'} to
> 'PyCFunction' {aka '_object* (*)(_object*, _object*)'}
> [-Werror=cast-function-type]
>   rec->def->ml_meth =
> reinterpret_cast(*dispatcher);
>
>
> Obviously as the error reports that the problem is cast between
> incompatible function types from 'PyObject' to 'PyCFunction'
>
> I installed all the required dependencies and as I am using fedora28 I
> installed:
>
> Python 2.7.14 and gcc-8.0.1-0.20.fc28.x86_64
>
> I hope you have a helpful guide in this issue.
> Thanks in advance.
> Best regards,
> Thawra
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] GEM5 Build error

[W . Shih]

Did you try cleaning the project and rebuild it?

After replacing the SWIG 2.0.4, I cleaned the project with scons -c and
rebuild it with SWIG 1.3.4, and it works for me.

Hope this helps.


___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] GEM5 Build error

[Muhammet ÖZGÜR]

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

On Tue, Dec 27, 2011 at 3:39 PM, Mahmood Naderan mahmood...@gmail.comwrote:

 Do you have any -Werror option in gem5/SConstruct?
 if yes, remove that.

 On 12/27/11, Muhammet ÖZGÜR muhammet@gmail.com 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::vectorProcess*, std::allocatorProcess* *
  std_vector_Sl_Process_Sm__SggetitemSWIG_0(std::vectorProcess*,
  std::allocatorProcess* *, 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__SgsetitemSWIG_0(std::vectorProcess*,
  std::allocatorProcess* *, PySliceObject*, const std::vectorProcess*,
  std::allocatorProcess* )':
  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__SgsetitemSWIG_1(std::vectorProcess*,
  std::allocatorProcess* *, 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__SgdelitemSWIG_1(std::vectorProcess*,
  std::allocatorProcess* *, 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 air...@yahoo.com
 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 muhammet@gmail.com
  *To:* gem5-users@gem5.org
  *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

Re: [gem5-users] GEM5 Build error

[Muhammet ÖZGÜR]

I am using version 1.3.40. I saw that page. I was using 2.0.4, then I
downgraded it to 1.3.40 but nothing changed...

On Tue, Dec 27, 2011 at 5:02 PM, Steve Reinhardt ste...@gmail.com wrote:

 What version of swig are you using?  See
 http://gem5.org/Dependencies#External_tools_and_required_versions


 2011/12/27 Muhammet ÖZGÜR muhammet@gmail.com

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


 On Tue, Dec 27, 2011 at 3:39 PM, Mahmood Naderan mahmood...@gmail.comwrote:

 Do you have any -Werror option in gem5/SConstruct?
 if yes, remove that.

 On 12/27/11, Muhammet ÖZGÜR muhammet@gmail.com 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::vectorProcess*, std::allocatorProcess* *
  std_vector_Sl_Process_Sm__SggetitemSWIG_0(std::vectorProcess*,
  std::allocatorProcess* *, 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__SgsetitemSWIG_0(std::vectorProcess*,
  std::allocatorProcess* *, PySliceObject*, const
 std::vectorProcess*,
  std::allocatorProcess* )':
  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__SgsetitemSWIG_1(std::vectorProcess*,
  std::allocatorProcess* *, 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__SgdelitemSWIG_1(std::vectorProcess*,
  std::allocatorProcess* *, 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 air...@yahoo.com
 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 muhammet@gmail.com
  *To:* gem5-users@gem5.org
  *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

Re: [gem5-users] GEM5 Build error

[Iordan Alexandru]

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 muhammet@gmail.com
To: gem5-users@gem5.org 
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
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

[gem5-users] GEM5 Build error

[Muhammet ÖZGÜR]

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
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users