[RTEMS Project] #3516: sb-set-builder should report disk usage of build

RTEMS trac trac at rtems.org
Sun Sep 16 00:00:09 UTC 2018

#3516: sb-set-builder should report disk usage of build
 Reporter:  Joel Sherrill  |       Owner:  Chris Johns
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  5.1
Component:  tool/rsb       |     Version:  5
 Severity:  normal         |  Resolution:
 Keywords:                 |  Blocked By:
 Blocking:                 |

Comment (by Joel Sherrill):

 Replying to [comment:4 Chris Johns]:
 > What do you define as space that needs to be accounted for?
 > 1. The build tree after each package in a build set has been built?
 > 2. Installed files?
 > 3. Source and patches?

 Good questions. The ultimate answer is all of that. :)

 The build tree peak is a critical piece of information. I saw people run
 out of disk space during the gcc/newlib phase. If we knew that, our
 instructions could give guidance. I did a no clean and was left with 8GB
 in build for SPARC. That's probably harsh if normally each package's build
 is cleaned. But SPARC now has more multilibs than I expected but arm and
 powerpc both have a lot also.

 The question is "how much do I need to build the tools for architecture
 X?" That includes source tarballs, git, patches, peak space for untar'ed,
 and peak build usage.
 And ideally we want to give advice that leaves people enough room to clone
 RTEMS and build it.

 How can we get the input to give good advice that avoids folks running out
 of build space during the "getting started"?

Ticket URL: <http://devel.rtems.org/ticket/3516#comment:5>
RTEMS Project <http://www.rtems.org/>
RTEMS Project

More information about the bugs mailing list