[Mesa-dev] Statically linking libstdc++ and libgcc

[Ilia Mirkin]

On Wed, Mar 11, 2015 at 12:40 PM, Ian Romanick <idr at freedesktop.org> wrote:
> On 03/11/2015 09:31 AM, Tobias Klausmann wrote:
>> The problem in not forcing this to link statically is, that if a
>> distribution decides to not use this static option, the problem persists
>> on that distribution. On top every lib pulled in by steam from the
>> system would need to be link statically, like mesa. Instead of fixing
>> every lib steam pulls in (how many are there?), fix the steam runtime to
>
> Yeah, static linking is a terrible, partial solution.

Actually seems like it's the only reasonable solution... For a
closed-source application provider who doesn't want to do builds
against every conceivable combination of their dependencies, they just
need to be moved into the binary and be done with it. (Although LGPL
might prevent that, not sure what the various licenses say about
linking statically vs dynamically.)

Of course the cat's out of the bag now, Valve probably can't go back
to all the publishers and say "relink your binaries statically or your
game won't work".

So the other alternative is that Steam provides a full bizarro world's
worth of libraries, which, like curro said, has to include libGL & co
as well. And/or a cross-compiler onto their bizarro world (which would
have the right binutils, gcc/libstdc++, etc).

  -ilia