rsb and toolchain debug symbols

Chris Johns chrisj at
Mon Aug 31 02:07:00 UTC 2020

On 30/8/20 2:17 am, Michael Davidsaver wrote:
> On 8/27/20 5:31 PM, Chris Johns wrote:
>> On 28/8/20 5:39 am, Michael Davidsaver wrote:
>>> Is there a way to ask RSB to either build the toolchain
>>> (ie. gcc itself) without debug symbols, or to strip them
>>> prior to install?
>> Not at the moment but this would be a nice feature. I can see it being needed.
>>> I keep a set of pre-built RTEMS pc*86 toolchains for use
>>> by CI builders, principally  In looking
>>> at adding RTEMS 5.1 to this I noticed that the resulting
>>> compressed tar was considerably larger that previously.
>>> 4.9 or 4.10 for pc386 are ~100MB, while 5.1 for pc686
>>> is weighing in at 380MB.
>>> Looking into it, most of this size seems to be in debug
>>> symbols.  eg. "libexec/gcc/i386-rtems5/7.5.0/cc1plus"
>>> is (uncompressed) 166MB with debug symbols and 26MB without.
>> That is a saving. The RSB could scan the tree of files before coping them to the
>> install point and for any host executable run the host's `strip` command. I
>> suppose we could also run it on any host archives if there is any easy way to
>> detect them.
> strip -d <prefix>/libexec/gcc/*/*/cc1*
> strip -d <prefix>/bin/*
> Gives ~50% reduction in compressed and uncompressed sizes without much effort.

Should the RSB strip host executables by default and provide an option to
disable stipping?

I had not given this topic any consideration before you raised it and I am now
wondering why I need tools installed with symbols.


More information about the users mailing list