Re: 3.5 package/binary size curiosity
Hi,
On Fri, Apr 06, 2012 at 10:58:42AM +0200, Dirk Griesbach wrote:
> Upgrading from 3.4.6, it needs about 70M more of space, while the
> upstream binary ist just about the same size as 3.4.6. For example,
> upstream libreoffice3.5/program/libooxlo.so is about 8M while in Debian
> it's 17M.
$ ls -lh libreoffice-core_3.4.6-2_amd64.deb libreoffice_3.5.2-1_amd64.deb
-rw-r--r-- 1 rene rene 49K 5. Apr 14:18 libreoffice_3.5.2-1_amd64.deb
-rw-r--r-- 1 rene rene 37M 23. Mär 01:18 libreoffice-core_3.4.6-2_amd64.deb
yeah.
But oox is a bad example, oox gained LOADS of data content in 3.5.x which
made it bigger (and so big that e.g. on ia64 you need to explicitely make
gcc optimize it for size with -Os to make it even link).
We don't use "special" options: I only can explain it with gcc 4.6 producing
bigger stuff than whatever ancient the official builds use (did 4.6 also be
bigger than upstream builds), but I more think that upstream might just build
with -Os.
Debian policy says "build with -O2".
Regards,
Rene
Reply to: