158387 - figure out libstdc++ linkage theory for mozilla builds with gcc >= 3.x

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect)

Description

[Dan Mosedale (:dmosedale, :dmose)]

For some value of x.  Need to determine what value of x is reasonable from both
a licensing and technical standpoint.

I'm starting off the investigation by comparing release builds with and without
a statically linked libstdc++ using gcc from the gcc 3.1 branch.  More info as I
see what the size/bloat implications of this are.

Comment 1

[Dan Mosedale (:dmosedale, :dmose)]

OK, so far so good:

Sizes of the exploded release tarball:

dynamic libstdc++: 31.13 megabytes
static libstdc++: 31.73 megabytes

difference: ~600K

Sizes of the gzipped tarballs themselves:

dynamic libstdc++: 12.06 megabytes
static libstdc++: 12.27 megabytes

difference: ~200K

The static builds were made by adding the following two lines to mozconfig:

CXX=gcc-31branch; export CXX
LIBS="-Wl,-Bstatic -lstdc++ -Wl,-Bdynamic"; export LIBS

Comment 2

[Dennis Haney]

You should use '-static-libgcc' instead. Not that I think it makes any difference ;)

Comment 3

[Bradley Baetz (:bbaetz)]

I suspect that static is only a small amount larger than dynamic because we use
no libstdc++ functions (except for operator new + friends).

Comment 4

[Dennis Haney]

How's it coming along?

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

All figured out.  Static linkage was chosen.

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

Fixed.