[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Fwd: hangup in make process

From: Eric Blossom
Subject: Re: [Discuss-gnuradio] Fwd: hangup in make process
Date: Sat, 18 Aug 2007 11:10:54 -0700
User-agent: Mutt/1.5.9i

On Fri, Aug 17, 2007 at 03:10:06AM -0700, vsrk sarma wrote:
> resending following query as no reply is posted. any advice?
> ---------- Forwarded message ----------
> From: vsrk sarma <address@hidden>
> Date: Aug 4, 2007 4:10 AM
> Subject: hangup in make process
> To: address@hidden
> I am trying to install gnuradio-3.0.3 on HP/Compaq nx6115 loaded with
> OpenSuSE10.2 64 bit (CD) version.
> after several unsuccessful attempts and amends, following GNU Radio
> components are successfully configured:
> gnuradio-core
> gnuradio-examples
> gr-audio-alsa
> gr-audio-oss
> gr-gsm-fr-vocoder
> gr-radio-astronomy
> gr-trellis
>  configure is failing for other components.
> However, 'make' process is hanging at the line:
> gnuraudio_swig_python.cc:3493 with warning:'dereferencing type-punned
> pointer will break strict-aliasing rules'
> Though such warning is seen in earlier lines of log process did not stop.
> similar message and hang-up is seen
>  when I try to 'make' only gnuradio-core. In both cases disk activity
> continues suggesting unending loop.
> Is it possible to rectify?
> Is it possible to run gr with only few components installed?
> Can software be tested without hardware installed?
> Is 512MB RAM adequate?

FYI, You didn't get an answer the first time, since you asked the same
question that was asked about 1 hour earlier on the same day.

Answer: 512MB is not adequate.  g++'s resident set size is about 750MB
when compiling some of our code.  This leads to constant paging on
small memory systems.  If you try building the svn trunk instead of
3.0.3 the footprint is smaller, but 512MB is still a bit on the small

Around here, 1GB of RAM is about 50 USD ;)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]