# Can no longer build packages for PPA

**URL:** <https://www.ruby-forum.com/t/can-no-longer-build-packages-for-ppa/237808>\
**Category:** GNU Radio\
**Created:** [December 1, 2013, 12:26pm UTC](https://www.ruby-forum.com/t/can-no-longer-build-packages-for-ppa/237808 "2013-12-01T12:26:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Detlef\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/58f4c7/32.png) [@Detlef\_R](https://www.ruby-forum.com/u/Detlef_R)\
**Post date:** [December 1, 2013, 12:26pm UTC](https://www.ruby-forum.com/t/can-no-longer-build-packages-for-ppa/237808/1 "2013-12-01T12:26:00Z")

</div>

Greetings,

Lately, I have been having increasing difficulties with building  
gnuradio successfully on the Ubuntu PPA builders. I think the problems  
is that the builds run in emulated environments and the builder is not  
as powerful as a modern desktop. Consequently, it will die on one of  
the swig files, either because of a 150 minutes timeout or it simply  
runs out of memory.

Initially, I only had this problem for some armhf builds and ignored  
it, but now with 3.7.2.1 amd64 builds are failing too ☹  
This could be due to reorganization of the build hosts but it is  
pretty much out of my control. I can try to request a rebuild hoping  
for a different build host from the pool, but it is a 10-15 hour wait  
and so far didn’t help.

Is there anything we can do in the gnuradio end to improve this?

Alex

---

<div class="post-metadata">

**Author:** ![copot](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/49beb7/32.png) [@copot](https://www.ruby-forum.com/u/copot)\
**Post date:** [December 3, 2013, 3:50pm UTC](https://www.ruby-forum.com/t/can-no-longer-build-packages-for-ppa/237808/2 "2013-12-03T15:50:15Z")

</div>

On Sun, Dec 1, 2013 at 6:24 AM, Alexandru C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> it, but now with 3.7.2.1 amd64 builds are failing too ☹  
> This could be due to reorganization of the build hosts but it is  
> pretty much out of my control. I can try to request a rebuild hoping  
> for a different build host from the pool, but it is a 10-15 hour wait  
> and so far didn’t help.
> 
> Is there anything we can do in the gnuradio end to improve this?
> 
> Alex

Hi Alex,

I don’t think there is, unfortunately. I’ve tried my best to split up  
the swig files to minimize the memory footprint and compile time, but  
it’s just too large a project.

Johnathan and I have been kicking around some ideas that might be able  
to help in the far future. But for right now, I haven’t found anything  
that can reduce the build issues further. I tried to go in an find as  
many instances of %include that can be replaced by %import, but there  
really weren’t that many.

One thing to do with the memory issue is to set make to only build  
with 1 thread (no parallelism). It’ll take longer over all, but it  
will keep the memory footprint pretty small. The main problem is when  
swigging multiple blocks\_swigX files at the same time.

Tom

---

<div class="post-metadata">

**Author:** ![copot](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/49beb7/32.png) [@copot](https://www.ruby-forum.com/u/copot)\
**Post date:** [December 3, 2013, 11:28pm UTC](https://www.ruby-forum.com/t/can-no-longer-build-packages-for-ppa/237808/3 "2013-12-03T23:28:01Z")

</div>

On Tue, Dec 3, 2013 at 3:48 PM, Tom R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > Initially, I only had this problem for some armhf builds and ignored  
> > Hi Alex,
> 
> One thing to do with the memory issue is to set make to only build  
> with 1 thread (no parallelism). It’ll take longer over all, but it  
> will keep the memory footprint pretty small. The main problem is when  
> swigging multiple blocks\_swigX files at the same time.

Hi Tom,

Thanks for the reply and the clarification. AFAIK the builds are  
already running single threaded although I am not 100% sure.

I managed to get the i386 and amd64 builds done this time by retrying  
the failed builds one more time. I guess I was lucky the third time.  
One solution might be to set up own PPA builder but I’m not quite  
there yet.

Alex
