This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH RFA: Build system: Check for -static-libstdc++


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]