Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus
On 2015-08-03 09:57, Basile Starynkevitch wrote:
> On Mon, Aug 03, 2015 at 09:47:33AM +0200, Aurelien Jarno wrote:
> > On 2015-04-30 23:10, Matthias Klose wrote:
> > > On 04/30/2015 10:43 PM, Daniel Serpell wrote:
> > > > Currently, gcc-5 packages are really big because the files under
> > > > /usr/lib/gcc/x86_64-linux-gnu/5 are not stripped, and each one of
> > > > lto1, cc1 and cc1plus is about 130MB.
> > > >
> > > > Please, can those files be striped in the default installation?
> > >
> > > I'd like to avoid this, and only change that near the next Debian release.
> > > These binaries are linked against libbacktrace to provide a verbose backtrace on
> > > internal compiler errors, which you can't get with stripped binaries.
> >
> > If that's not possible could you please at least change these binaries to
> > use compressed debug sections at least? That should save quite some space
> > already.
>
> I would believe that is not easily possible. I don't know the detailed
> behavior of libbacktrace, but it is using & parsing the DWARF debug
> information of the binaries (cc1, cc1plus, ...), so I guess you'll need
> to patch (significantly) libbacktrace to compress the debug sections.
compressed debug sections is kind of standard these days, so
libbacktrace should support that.
> BTW, I don't see the size of cc1 etc... as an issue. Compilers are
> useful on "development" machines, and these are usually not very small
> (and have enought disk space).
This adds roughly 1GB to the size of a chroot used on the Debian build
daemons. As it is unpacked from a tarball for each package to build, it
has a significant impact on the time needed to unpack the chroot.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: