>>>> "MB" == Martin Buchholz
<martin(a)xemacs.org> writes:
>>>> "juhp" == Jens-Ulrik Petersen
<petersen(a)kurims.kyoto-u.ac.jp> writes:
juhp> I am curious, can someone explain to me why for me XEmacs
juhp> binaries built under Sparc/Solaris-2+gcc-2.8 are always so
juhp> much larger than XEmacs binaries built under Intel/Linux?
juhp> -rwxr-xr-x 1 petersen 19678112 May 13 13:37 solaris/bin/xemacs*
juhp> I don't have the exact size of my Linux xemacs* binary but I
juhp> seem to recall that it is of the order of 3+Mb. Why is the
juhp> Solaris binary 5 times larger?
MB> My previous posting to this mailing list suggested that
MB> Solaris binaries should be just a little larger.
MB> Linux, egcs 1.0.2, CFLAGS=-O2: 2314155 Linux, egcs 1.0.2,
MB> CFLAGS=-O3: 2441153
MB> Solaris, egcs 1.0.2, CFLAGS=-O2: 2843084 Solaris, egcs 1.0.2,
MB> CFLAGS=-O3: 2963692
MB> But I look at my debug builds, and they are almost as big as
MB> yours:
MB> Solaris, egcs 1.0.2, CFLAGS=-g: 18146604
MB> It is very likely to be debug information that is repeated in
MB> all the .o files.
Thanks Martin. I think that is the simple explanation I was looking
for. I forget (to say) that I build XEmacs without debugging on my
little i486 at home.... I didn't realize that debugging info makes
such a huge difference in binary size.
Cheers,
--
Jens-Ulrik Holger Petersen <
http://www.kurims.kyoto-u.ac.jp/~petersen/>
Research Institute for Mathematical Sciences, Kyoto University