This is the mail archive of the
mailing list for the GCC project.
Re: PATCH RFA: Build system: Check for -static-libstdc++
- From: Mike Stump <mikestump at comcast dot net>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 3 Nov 2010 10:28:59 -0700
- Subject: Re: PATCH RFA: Build system: Check for -static-libstdc++
- References: <email@example.com>
On Nov 2, 2010, at 9:36 PM, Ian Lance Taylor wrote:
> The Go frontend wants to use it when linking, so that the Go frontend is
> independent of the installed libstdc++.so. This is particularly useful
> when bootstrapping, and is generally desirable as it permits moving the
> compiler around.
I don't think this is the way forward. A platform selects shared or non-shared libraries for platform reasons. You ignore those reasons and seek to change them. If everyone did that, we'd be back in 1989 with software installations that are 20x or more of what they should be. So, my question, is what makes go so special that the default should not apply?
People that move the compiler around, are already aware of the magic games they have to play with the shared libraries.